-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable libvirt proxy local socket #1607
base: master
Are you sure you want to change the base?
Conversation
Hi @psathyan. Thanks for your PR. I'm waiting for a openshift-metal3 member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This PR includes a proposed a patch (1607) [openshift-metal3/dev-scripts#1607] that may improve the reliability of OCP deployment and avoid observing the below error 2023-11-23 15:20:02 level=error msg=Error: failed to dial libvirt: dial unix /var/run/libvirt/libvirt-sock: connect: no such file or directory Signed-off-by: Pragadeeswaran Sathyanarayanan <psathyan@redhat.com>
/ok-to-test |
/test e2e-metal-ipi-ovn-dualstack |
This PR includes a proposed a patch (1607) [openshift-metal3/dev-scripts#1607] that may improve the reliability of OCP deployment and avoid observing the below error 2023-11-23 15:20:02 level=error msg=Error: failed to dial libvirt: dial unix /var/run/libvirt/libvirt-sock: connect: no such file or directory Signed-off-by: Pragadeeswaran Sathyanarayanan <psathyan@redhat.com>
This PR includes a proposed a patch (1607) [openshift-metal3/dev-scripts#1607] that may improve the reliability of OCP deployment and avoid observing the below error 2023-11-23 15:20:02 level=error msg=Error: failed to dial libvirt: dial unix /var/run/libvirt/libvirt-sock: connect: no such file or directory Signed-off-by: Pragadeeswaran Sathyanarayanan <psathyan@redhat.com>
/test e2e-metal-ipi-bm-bond |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Confirming that this also works for me.
/retest |
/retest-required |
2 similar comments
/retest-required |
/retest-required |
/retest-required |
/retest-required |
2023-11-23 15:20:02 level=error msg=Error: failed to dial libvirt: dial unix /var/run/libvirt/libvirt-sock: connect: no such file or directory There some lingering runs having the above error message. Hence, enabling virtproxyd service Signed-off-by: Pragadeeswaran Sathyanarayanan <psathyan@redhat.com>
@psathyan: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested and this fixes dev-scripts on a fresh Stream 9 installations
/approve |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mkowalski The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest-required |
We have observed the below error in some of our deployments.
Using this patch, we are able to proceed when the above error is observed. Newer deployments with this patch have been successful.