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

Bump ovs-cni to 0.8.0 #267

Merged
merged 1 commit into from
Nov 29, 2019
Merged

Bump ovs-cni to 0.8.0 #267

merged 1 commit into from
Nov 29, 2019

Conversation

qinqon
Copy link
Collaborator

@qinqon qinqon commented Nov 28, 2019

To include the bridge reporting fix [1]

[1] k8snetworkplumbingwg/ovs-cni#93

Signed-off-by: Quique Llorente [email protected]

@kubevirt-bot kubevirt-bot added dco-signoff: yes Indicates the PR's author has DCO signed all their commits. size/XS labels Nov 28, 2019
@qinqon qinqon requested a review from phoracek November 28, 2019 15:59
@phoracek
Copy link
Member

@qinqon don't forget to update test/releases

@phoracek
Copy link
Member

The marker also fails with:

[phoracek@t470s cluster-network-addons-operator]$ ./cluster/kubectl.sh logs -n cluster-network-addons ovs-cni-amd64-4vqm5 -c ovs-cni-marker
F1128 19:01:51.701489       1 main.go:42] failed to create a new marker object: Error creating the ovsdb connection: failed to connect to ovsdb error: Invalid socket file

@phoracek
Copy link
Member

We gotta update the manifest, it has been changed on ovs-cni in k8snetworkplumbingwg/ovs-cni#80.

@qinqon
Copy link
Collaborator Author

qinqon commented Nov 29, 2019

deploying and activaing OVS works fine.
but CI fails at

F1129 11:03:14.970689       1 main.go:42] failed to create a new marker object: Error creating the ovsdb connection: failed to connect to ovsdb error: Invalid socket file

We have to install ovs at nodes, why we didn't need it before ? the socket was created by container if does not exists ?

@qinqon qinqon force-pushed the ovs-cni_0.8.0 branch 3 times, most recently from 1103511 to 8f8e702 Compare November 29, 2019 13:09
@phoracek
Copy link
Member

That's what I commented. The difference is in the format of the socket parameter.

@qinqon
Copy link
Collaborator Author

qinqon commented Nov 29, 2019

Also the path, /run/openvswitch is no good. Now it has all it needs also I think we no longer need localbin since we are not using ovs-vsctl

@@ -135,9 +135,7 @@ systemctl start NetworkManager
## Open vSwitch

The operator allows administrator to deploy [OVS CNI plugin](https://github.com/kubevirt/ovs-cni/)
simply by adding `ovs` attribute to `NetworkAddonsConfig`. Please note that
Copy link
Member

Choose a reason for hiding this comment

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

Please say that openvswitch has to be running on the node.

To include the bridge reporting fix [1]

[1] k8snetworkplumbingwg/ovs-cni#93

Signed-off-by: Quique Llorente <[email protected]>
@phoracek phoracek merged commit 6232740 into kubevirt:master Nov 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dco-signoff: yes Indicates the PR's author has DCO signed all their commits. size/S
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants