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
Bug 1798191: Bump to ovn2.12 #445
Conversation
/test e2e-aws-ovn |
/test e2e-aws-ovn |
/test e2e-aws-ovn |
1 similar comment
/test e2e-aws-ovn |
/test e2e-aws-ovn |
/test e2e-aws-ovn |
@alexanderConstantinescu @rcarrillocruz @dcbw PTAL |
@@ -70,7 +70,7 @@ spec: | |||
|
|||
exec ovn-northd \ | |||
--no-chdir "-vconsole:${OVN_LOG_LEVEL}" -vfile:off \ | |||
--pidfile=/var/run/openvswitch/ovn-northd.pid \ | |||
--pidfile=ovn-northd.pid \ |
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.
According to the man pages (at least for 2.11) this will make it put the pidfile in .
However, do we actually need to be writing the pid files at all? It looks like the only pid file we ever read is the ovn-nbctl daemon's, and the others are "write-only" and we could just remove the --pidfile
arguments...
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.
Changed. Dropped unneeded pid files.
@@ -330,7 +336,7 @@ spec: | |||
fi | |||
|
|||
# start nbctl daemon for caching | |||
export OVN_NB_DAEMON=$(ovn-nbctl --pidfile=/run/openvswitch/ovnk-nbctl.pid \ | |||
export OVN_NB_DAEMON=$(ovn-nbctl --pidfile=ovnk-nbctl.pid \ |
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.
the container's preStop
hook still does kill $(cat /run/openvswitch/ovnk-nbctl.pid)
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.
fixed
@@ -394,7 +402,11 @@ spec: | |||
hostPath: | |||
path: /var/lib/ovn/data | |||
- name: run-openvswitch | |||
emptyDir: {} | |||
hostPath: | |||
path: /var/run/openvswitch |
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.
This makes it so that the container's /run/openvswitch
would be preserved between runs of different containers, which I don't think we want...
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.
So, if I am not mistaken (and I think I would like to "call a friend" on this one: @dcbw ). Those locations contain the OVN DB. Which we do not want to preserve between runs because:
- I am pretty sure we can not upgrade and will crash when going from non-HA -> HA and vice versa (if we would ever, not sure we would though as non-HA is only in version 4.1/4.2 - tech-preview?)
- Our source of truth is k8s and we sync directly with it on startup anyways, and thus re-write the DB.
So, yes, I don't think we want this.
Why did you add this though @pecameron ? Is it required for 2.12?
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.
The unix socket needs to be everywhere it is referenced. This fixed the problem.
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.
This actually passes tests. I will back out the change.
/test e2e-aws-ovn |
/test e2e-aws-ovn |
No nodes, no pods.... |
"Error: ResourceLimitExceeded: Task limit exceeded" |
tcp 10.0.140.52:6443: connect: connection refused |
Cant't reach api server |
/test e2e-aws-ovn |
/retest |
1 similar comment
/retest |
level=error msg="Cluster operator openshift-etcd Degraded is True with ConfigObservationDegradedError: ConfigObservationDegraded: error looking up self: lookup _etcd-server-ssl._tcp.ci-op-nd4331wx-583c6.origin-ci-int-aws.dev.rhcloud.com on 172.30.0.10:53: read udp 10.129.0.21:43654->172.30.0.10:53: i/o timeout\nConfigObservationDegraded: error looking up self: lookup _etcd-server-ssl._tcp.ci-op-nd4331wx-583c6.origin-ci-int-aws.dev.rhcloud.com on 172.30.0.10:53: read udp 10.129.0.21:55834->172.30.0.10:53: i/o timeout" /retest |
Different set of failures this time. Trying again. |
/retest |
e2e-aws-ovn |
@dcbw 445 passed tests. @alexanderConstantinescu @danwinship @rcarrillocruz Can we get this in? PTAL. I need it to test PR72 ovn2.12 image. |
New paths for components pidfile changes. SDN-643 Signed-off-by: Phil Cameron <pcameron@redhat.com>
/test e2e-aws-ovn |
Back to a flaky CI.... |
/test e2e-gcp-ovn |
/test e2e-aws-ovn |
/lgtm |
@pecameron: This pull request references Bugzilla bug 1798191, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
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. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dcbw, pecameron 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. |
@pecameron: All pull requests linked via external trackers have merged. Bugzilla bug 1798191 has been moved to the MODIFIED state. In response to this:
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. |
@pecameron: The following test failed, say
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. |
New paths for components
SDN-643
Signed-off-by: Phil Cameron pcameron@redhat.com