Skip to content
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

Adds missing OVN NB SSL args to ovnkube master #572

Merged
merged 1 commit into from Apr 7, 2020

Conversation

trozet
Copy link
Contributor

@trozet trozet commented Apr 6, 2020

For OVN NB DB interaction with the ovn-nbctl command, we use ovn-nbctl
daemon mode, where we do not need to use SSL arguments to directly
interact with the nbctl socket in the pod. However, SSL arguments are
needed for non-nbctl commands like ovsdb client. This patch adds those
arguments.

In addition, the nbctl-daemon-mode argument was missing as well. This
argument indicates to ovn-kubernetes that it needs to use nbctl daemon
mode. Even though we were previously not setting this, we were exporting
the proper bash env var to allow the process to automatically use daemon
mode. However, we should pass the correct arguments to be consistent.
Due to an OVN bug, we need to temporarily symlink the ovn-nbctl control
socket to /var/run/ovn as it is accidentally placed in
/var/run/openvswitch today.

Signed-off-by: Tim Rozet trozet@redhat.com

@trozet
Copy link
Contributor Author

trozet commented Apr 6, 2020

@dcbw @danwinship PTAL

@trozet
Copy link
Contributor Author

trozet commented Apr 6, 2020

/test e2e-gcp-ovn
/test e2e-aws-ovn

@dcbw
Copy link
Contributor

dcbw commented Apr 6, 2020

Build issues?

/retest

@trozet
Copy link
Contributor Author

trozet commented Apr 6, 2020

It almost passed ovn-aws, but needs:
openshift/origin#24833

@abhat
Copy link
Contributor

abhat commented Apr 7, 2020

/retest

Copy link
Contributor

@pecameron pecameron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 7, 2020
@danwinship
Copy link
Contributor

So is there some underlying bug that you're fixing? Or is this just code cleanliness?

@abhat
Copy link
Contributor

abhat commented Apr 7, 2020

So is there some underlying bug that you're fixing? Or is this just code cleanliness?

The PR is needed for go-ovn bindings when we get rid of the shell invocations.

@trozet
Copy link
Contributor Author

trozet commented Apr 7, 2020

So is there some underlying bug that you're fixing? Or is this just code cleanliness?

The PR is needed for go-ovn bindings when we get rid of the shell invocations.

@danwinship it's needed right now because with the SCTP code we use ovsdbclient to check if OVN supports SCTP, and to do that we need NB SSL args.

@trozet
Copy link
Contributor Author

trozet commented Apr 7, 2020

/retest

@trozet
Copy link
Contributor Author

trozet commented Apr 7, 2020

/assign @knobunc

@dcbw
Copy link
Contributor

dcbw commented Apr 7, 2020

/approve

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 7, 2020
For OVN NB DB interaction with the ovn-nbctl command, we use ovn-nbctl
daemon mode, where we do not need to use SSL arguments to directly
interact iwth the nbctl socket in the pod. However, SSL arguments are
needed for non-nbctl commands like ovsdb client. This patch adds those
arguments.

In addition, the nbctl-daemon-mode argument was missing as well. This
argument indicates to ovn-kubernetes that it needs to use nbctl daemon
mode. Even though we were previously not setting this, we were exporting
the proper bash env var to allow the process to automatically use daemon
mode. However, we should pass the correct arguments to be consistent.
Due to an OVN bug, we need to temporarily symlink the ovn-nbctl control
socket to /var/run/ovn as it is accidentally placed in
/var/run/openvswitch today.

Signed-off-by: Tim Rozet <trozet@redhat.com>
@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Apr 7, 2020
@dcbw
Copy link
Contributor

dcbw commented Apr 7, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 7, 2020
@abhat
Copy link
Contributor

abhat commented Apr 7, 2020

/lgtm

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhat, dcbw, pecameron, trozet

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Apr 7, 2020

@trozet: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-ovn-step-registry 6749b22 link /test e2e-ovn-step-registry
ci/prow/e2e-aws-ovn 6749b22 link /test e2e-aws-ovn
ci/prow/e2e-ovn-hybrid-step-registry 3a85ce8 link /test e2e-ovn-hybrid-step-registry
ci/prow/e2e-gcp-ovn 3a85ce8 link /test e2e-gcp-ovn

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants