Skip to content
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.

unsupported OVS_ACTION_ATTR_SET attribute 0 on coreOS 877.1.0 #1854

Closed
enxebre opened this issue Jan 5, 2016 · 10 comments
Closed

unsupported OVS_ACTION_ATTR_SET attribute 0 on coreOS 877.1.0 #1854

enxebre opened this issue Jan 5, 2016 · 10 comments

Comments

@enxebre
Copy link

enxebre commented Jan 5, 2016

Hi,
I am having unsupported OVS_ACTION_ATTR_SET attribute 0 on coreOS 877.1.0
when weave launch
I'm guessing related to openvswitch changes on linux 4.3 https://lwn.net/Articles/662714/

weave version 1.4.1
coreOS 877.1.0

Thanks

@bboreham
Copy link
Contributor

bboreham commented Jan 5, 2016

Interesting, I don't get that when I try.

Could you supply details of the commands used to launch, plus full logs from docker logs weave?

@bboreham
Copy link
Contributor

bboreham commented Jan 5, 2016

On further testing, I do get something similar if I stop then re-launch weave:

core@ip-172-31-46-228 ~ $ ./weave launch-router 172.31.46.229
2fb3a61b029e39165a959b09319f9639de2c36d61862121ed4b29951fedf9c2b
core@ip-172-31-46-228 ~ $ ./weave stop-router
core@ip-172-31-46-228 ~ $ ./weave launch-router 172.31.46.229
The weave container has died. Consult the container logs for further details.
core@ip-172-31-46-228 ~ $ docker logs weave
INFO: 2016/01/05 16:46:35.372920 Command line options: map[ipalloc-range:10.32.0.0/12 name:1a:90:49:e6:2e:70 nickname:ip-172-31-46-228.eu-west-1.compute.internal port:6783 datapath:datapath dns-effective-listen-address:172.17.0.1 dns-listen-address:172.17.0.1:53 http-addr:127.0.0.1:6784]
INFO: 2016/01/05 16:46:35.372997 Command line peers: [172.31.46.229]
FATA: 2016/01/05 16:46:35.392626 unsupported OVS_ACTION_ATTR_SET attribute 4

@rade rade added the bug label Jan 5, 2016
@bboreham
Copy link
Contributor

bboreham commented Jan 5, 2016

In this situation, weave reset then weave launch lets it work again, for me.

@rade rade added this to the 1.4.2 milestone Jan 5, 2016
@bboreham
Copy link
Contributor

bboreham commented Jan 5, 2016

Seems similar to weaveworks/go-odp#4

@enxebre
Copy link
Author

enxebre commented Jan 6, 2016

@bboreham weave reset then weave launch works
Thanks

@dpw
Copy link
Contributor

dpw commented Jan 6, 2016

Might be of interest that I couldn't reproduce this in my VM running kernel 4.4rc8. I had to reboot it into 4.3 to reproduce.

So I wonder if this is not due to new CT attributes in 4.3 as I had assumed, but rather is related to this: http://thread.gmane.org/gmane.network.openvswitch.devel/56655

@bboreham
Copy link
Contributor

bboreham commented Jan 7, 2016

Seems to have been introduced by torvalds/linux@fc4099f

While transitioning to netdev based vport we broke OVS feature [...]

and fixing that caused this breakage.

(thanks for info @rade)

@dpw
Copy link
Contributor

dpw commented Jan 9, 2016

See comments on weaveworks/go-odp#4. Should be fixed now with an updated go-odp.

@bboreham
Copy link
Contributor

@dpw I think you might have meant weaveworks/go-odp#5. Commits are weaveworks/go-odp@5d06488 and weaveworks/go-odp@c794b8c, thanks!

@awh
Copy link
Contributor

awh commented Jan 12, 2016

Fixed by weaveworks/go-odp@c794b8c.

@awh awh closed this as completed Jan 12, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants