← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 2020771] [NEW] [ml2/ovn] Binding_host_id shouldn't be set when a port is down

 

Public bug reported:

Currently e.g if you shelve an instance, the port for it is set to DOWN
but the `binding_host_id` still exist for that port. And with sync to
OVN Northbound `Logical_Switch_Port` table it is populated to
`options:requested_chassis`. Which shouldn't be the case.


That also lead to northd throwing out these warnings, if that chassis got removed in the mean time:


```
northd|WARN|Unknown chassis '<chassis>' set in options:requested-chassis on LSP '<uuid>'
```


neutron version: stable/yoga

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2020771

Title:
  [ml2/ovn] Binding_host_id shouldn't be set when a port is down

Status in neutron:
  New

Bug description:
  Currently e.g if you shelve an instance, the port for it is set to
  DOWN but the `binding_host_id` still exist for that port. And with
  sync to OVN Northbound `Logical_Switch_Port` table it is populated to
  `options:requested_chassis`. Which shouldn't be the case.

  
  That also lead to northd throwing out these warnings, if that chassis got removed in the mean time:

  
  ```
  northd|WARN|Unknown chassis '<chassis>' set in options:requested-chassis on LSP '<uuid>'
  ```

  
  neutron version: stable/yoga

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2020771/+subscriptions