nova-compute restart leads to instance downtime when isolate_vif=True is used
Bug #2023300 reported by
Vasyl Saienko
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
os-vif |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Since nova moved to use os-vifs library to initialise interfaces and when isolate_vif is set to True
https:/
During nova-compute service restart it calls plug_vifs https:/
Changed in os-vif: | |
status: | New → In Progress |
To post a comment you must log in.
Reviewed: https:/ /review. opendev. org/c/openstack /os-vif/ +/885127 /opendev. org/openstack/ os-vif/ commit/ 0a0dec37e42e220 ffa750650027714 bd7289faa1
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 0a0dec37e42e220 ffa750650027714 bd7289faa1
Author: Vasyl Saienko <email address hidden>
Date: Fri Jun 2 11:52:59 2023 +0000
Don't break traffic if port already exists
Nova compute service plugs VIF on service init, it triggers
rules reinitialization for iptables filter. But it breaks
traffic in case isolate_vif is used by assigning dead VLAN
to the port. This patch prevents dead VLAN assingment
for ports that exists.
Co-Authored-By: <email address hidden>
Closes-Bug: #2023300
Change-Id: Ib1b7467fce9fac fbfcd698bf6e9f9 50c0cead650