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
sdn: use the correct socket path #451
sdn: use the correct socket path #451
Conversation
/test e2e-gcp-upgrade |
This fix is correct, but I think that code is useless anyway... as far as I remember, it was originally added (in openshift-ansible) to handle the case of upgrading from openshift-sdn running directly on the node to openshift-sdn running in a container, where it was difficult to synchronize the switchover for some reason. The check got copied over from openshift-ansible to cluster-network-operator in 4.0, but with sdn always running in a pod now, there shouldn't ever be any case where a new openshift-sdn process gets started while the old one is still running... I was going to say "we should look through CI logs to see if the warning ever gets printed", except of course that since the check was broken, we know it doesn't. So, OK, let's merge this now and then check later... /lgtm |
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danwinship, pecameron, rphillips The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest Please review the full test history for this PR and help us cut down flakes. |
Fix the socket path for the cni server socket