Public bug reported:
While upgrading to rocky, we ended up with a broken openvswitch
infrastructure and moved back to the old openvswitch.
We ended up with new machines working, old machines didn't and it took a
while to realize that we had qvo* interfaces that not only wasn't
plugged but also wasn't owned by ovs-system - basically the virtual
equivalent of forgetting to plug in the cable ;)
This was quickly addressed by running this bash-ism on all nodes:
for x in `ip a |grep qvo |grep @qvb |grep -v ovs-system | awk '{ print $2 '}` ;
do y=${x%%"@"*} && ip link delete $y ; done ; docker restart nova_compute
However, nova could pretty easily sanity check this =)
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1815762
Title:
you can end up in a state where qvo* interfaces aren't owned by ovs
which results in a dangling connection
Status in OpenStack Compute (nova):
New
Bug description:
While upgrading to rocky, we ended up with a broken openvswitch
infrastructure and moved back to the old openvswitch.
We ended up with new machines working, old machines didn't and it took
a while to realize that we had qvo* interfaces that not only wasn't
plugged but also wasn't owned by ovs-system - basically the virtual
equivalent of forgetting to plug in the cable ;)
This was quickly addressed by running this bash-ism on all nodes:
for x in `ip a |grep qvo |grep @qvb |grep -v ovs-system | awk '{ print $2 '}`
; do y=${x%%"@"*} && ip link delete $y ; done ; docker restart nova_compute
However, nova could pretty easily sanity check this =)
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1815762/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
