[Bug 1958843] [NEW] VIF Plug Provider not recreating port on change of netdev name

Frode Nordahl 1958843 at bugs.launchpad.net
Mon Jan 24 09:12:50 UTC 2022 

Public bug reported:

At present, if a port is first plugged by OVN through the VIF Plug
Provider framework [0], and then subsequent changes to LSP options lead
to change of netdev name, the VIF Plug Provider framework will refuse to
update the port.

A port can get into this situation when the CMS performs life cycle
management of an existing instance. For example if CMS is OpenStack, and
you perform resize of an instance to the same hypervisor. In this
situation the LSP will be re-used but Nova will allocate a new VF for
the port.

Change of VF also means change of which representor port is associated
with a given lport.

Currently resize to same hypervisor will fail and OVN will log the following:
2022-01-22T16:12:51.987Z|03813|vif_plug|WARN|Attempt of incompatible change to existing port detected, please recreate port: 3844eaf7-4bda-40e2-b9a0-d8b5e85a06b1

The code in OVN behaves this way because OVS port/interface name is
immutable, but it could choose to unplug/plug the port instead of just
logging a warning.

0: https://docs.ovn.org/en/stable/topics/vif-plug-providers/vif-plug-
providers.html

** Affects: ovn (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

  At present, if a port is first plugged by OVN through the VIF Plug
  Provider framework [0], and then subsequent changes to LSP options lead
  to change of netdev name, the VIF Plug Provider framework will refuse to
  perform plug/unplug operations for the port.
  
  A port can get into this situation when the CMS performs life cycle
  management of an existing instance. For example if CMS is OpenStack, and
  you perform resize of an instance to the same hypervisor. In this
  situation the LSP will be re-used but Nova will associate a new VF for
  the port.
  
  Currently resize to same hypervisor will fail and OVN will log the following:
  2022-01-22T16:12:51.987Z|03813|vif_plug|WARN|Attempt of incompatible change to existing port detected, please recreate port: 3844eaf7-4bda-40e2-b9a0-d8b5e85a06b1
  
  The code in OVN behaves this way because OVS port/interface name is
  immutable, but it could choose to unplug/plug the port instead of just
  logging a warning.
+ 
+ 0: https://docs.ovn.org/en/stable/topics/vif-plug-providers/vif-plug-
+ providers.html

** Description changed:

  At present, if a port is first plugged by OVN through the VIF Plug
  Provider framework [0], and then subsequent changes to LSP options lead
  to change of netdev name, the VIF Plug Provider framework will refuse to
  perform plug/unplug operations for the port.
  
  A port can get into this situation when the CMS performs life cycle
  management of an existing instance. For example if CMS is OpenStack, and
  you perform resize of an instance to the same hypervisor. In this
- situation the LSP will be re-used but Nova will associate a new VF for
+ situation the LSP will be re-used but Nova will allocate a new VF for
  the port.
  
  Currently resize to same hypervisor will fail and OVN will log the following:
  2022-01-22T16:12:51.987Z|03813|vif_plug|WARN|Attempt of incompatible change to existing port detected, please recreate port: 3844eaf7-4bda-40e2-b9a0-d8b5e85a06b1
  
  The code in OVN behaves this way because OVS port/interface name is
  immutable, but it could choose to unplug/plug the port instead of just
  logging a warning.
  
  0: https://docs.ovn.org/en/stable/topics/vif-plug-providers/vif-plug-
  providers.html

** Description changed:

  At present, if a port is first plugged by OVN through the VIF Plug
  Provider framework [0], and then subsequent changes to LSP options lead
  to change of netdev name, the VIF Plug Provider framework will refuse to
- perform plug/unplug operations for the port.
+ update the port.
  
  A port can get into this situation when the CMS performs life cycle
  management of an existing instance. For example if CMS is OpenStack, and
  you perform resize of an instance to the same hypervisor. In this
  situation the LSP will be re-used but Nova will allocate a new VF for
  the port.
  
  Currently resize to same hypervisor will fail and OVN will log the following:
  2022-01-22T16:12:51.987Z|03813|vif_plug|WARN|Attempt of incompatible change to existing port detected, please recreate port: 3844eaf7-4bda-40e2-b9a0-d8b5e85a06b1
  
  The code in OVN behaves this way because OVS port/interface name is
  immutable, but it could choose to unplug/plug the port instead of just
  logging a warning.
  
  0: https://docs.ovn.org/en/stable/topics/vif-plug-providers/vif-plug-
  providers.html

** Description changed:

  At present, if a port is first plugged by OVN through the VIF Plug
  Provider framework [0], and then subsequent changes to LSP options lead
  to change of netdev name, the VIF Plug Provider framework will refuse to
  update the port.
  
  A port can get into this situation when the CMS performs life cycle
  management of an existing instance. For example if CMS is OpenStack, and
  you perform resize of an instance to the same hypervisor. In this
  situation the LSP will be re-used but Nova will allocate a new VF for
  the port.
  
+ Change of VF also means change of which representor port is associated
+ with a given lport.
+ 
  Currently resize to same hypervisor will fail and OVN will log the following:
  2022-01-22T16:12:51.987Z|03813|vif_plug|WARN|Attempt of incompatible change to existing port detected, please recreate port: 3844eaf7-4bda-40e2-b9a0-d8b5e85a06b1
  
  The code in OVN behaves this way because OVS port/interface name is
  immutable, but it could choose to unplug/plug the port instead of just
  logging a warning.
  
  0: https://docs.ovn.org/en/stable/topics/vif-plug-providers/vif-plug-
  providers.html

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to ovn in Ubuntu.
https://bugs.launchpad.net/bugs/1958843

Title:
  VIF Plug Provider not recreating port on change of netdev name

Status in ovn package in Ubuntu:
  New

Bug description:
  At present, if a port is first plugged by OVN through the VIF Plug
  Provider framework [0], and then subsequent changes to LSP options
  lead to change of netdev name, the VIF Plug Provider framework will
  refuse to update the port.

  A port can get into this situation when the CMS performs life cycle
  management of an existing instance. For example if CMS is OpenStack,
  and you perform resize of an instance to the same hypervisor. In this
  situation the LSP will be re-used but Nova will allocate a new VF for
  the port.

  Change of VF also means change of which representor port is associated
  with a given lport.

  Currently resize to same hypervisor will fail and OVN will log the following:
  2022-01-22T16:12:51.987Z|03813|vif_plug|WARN|Attempt of incompatible change to existing port detected, please recreate port: 3844eaf7-4bda-40e2-b9a0-d8b5e85a06b1

  The code in OVN behaves this way because OVS port/interface name is
  immutable, but it could choose to unplug/plug the port instead of just
  logging a warning.

  0: https://docs.ovn.org/en/stable/topics/vif-plug-providers/vif-plug-
  providers.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1958843/+subscriptions

More information about the Ubuntu-openstack-bugs mailing list