diff options
| author | Balazs Gibizer <gibi@redhat.com> | 2022-07-15 13:48:46 +0200 |
|---|---|---|
| committer | Balazs Gibizer <gibi@redhat.com> | 2022-09-08 09:19:16 +0200 |
| commit | e43bf900dc8ca66578603bed333c56b215b1876e (patch) | |
| tree | c23f6fc1af2445efcb0d0636d4788c89fa7c1f24 /releasenotes/notes | |
| parent | f8c91eb75fc5504a37fc3b4be1d65d33dbc9b511 (diff) | |
| download | nova-e43bf900dc8ca66578603bed333c56b215b1876e.tar.gz | |
Gracefully ERROR in _init_instance if vnic_type changed
If the vnic_type of a bound port changes from "direct" to "macvtap" and
then the compute service is restarted then during _init_instance nova
tries to plug the vif of the changed port. However as it now has macvtap
vnic_type nova tries to look up the netdev of the parent VF. Still that
VF is consumed by the instance so there is no such netdev on the host
OS. This error killed the compute service at startup due to unhandled
exception. This patch adds the exception handler, logs an ERROR and
continue initializing other instances on the host.
Also this patch adds a detailed ERROR log when nova detects that the
vnic_type changed during _heal_instance_info_cache periodic.
Closes-Bug: #1981813
Change-Id: I1719f8eda04e8d15a3b01f0612977164c4e55e85
Diffstat (limited to 'releasenotes/notes')
| -rw-r--r-- | releasenotes/notes/bug-1981813-vnic-type-change-9f3e16fae885b57f.yaml | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/releasenotes/notes/bug-1981813-vnic-type-change-9f3e16fae885b57f.yaml b/releasenotes/notes/bug-1981813-vnic-type-change-9f3e16fae885b57f.yaml new file mode 100644 index 0000000000..a5a3b7c8c2 --- /dev/null +++ b/releasenotes/notes/bug-1981813-vnic-type-change-9f3e16fae885b57f.yaml @@ -0,0 +1,9 @@ +--- +fixes: + - | + `Bug #1981813 <https://bugs.launchpad.net/nova/+bug/1981813>`_: Now nova + detects if the ``vnic_type`` of a bound port has been changed in neutron + and leaves an ERROR message in the compute service log as such change on a + bound port is not supported. Also the restart of the nova-compute service + will not crash any more after such port change. Nova will log an ERROR and + skip the initialization of the instance with such port during the startup. |