neutron

  1. Bug #2024160
  2. Comment #18

Comment 18 for bug 2024160

Revision history for this message
Mohammed Naser (mnaser) wrote (last edit ):

So the thing that I noticed is that I assume there are no addresses assigned for the sub-ports, so what happens seems to be this in the `ovn-controller` logs:

```
2023-09-22T20:15:38.402Z|380055|binding|INFO|Claiming lport c6858836-2ef8-4259-bf30-e7d769d8c165 for this chassis.
2023-09-22T20:15:38.402Z|380056|binding|INFO|c6858836-2ef8-4259-bf30-e7d769d8c165: Claiming unknown
```

But I'm not seeing the same output as a usual virtual port...

```
2023-09-22T20:15:47.959Z|380057|pinctrl|INFO|Claiming virtual lport fa57424b-3228-4b29-9bb4-c6edb7927a5f for this chassis with the virtual parent cb15f805-943d-4efa-9646-7a700e6cd81b
2023-09-22T20:15:52.853Z|380058|pinctrl|INFO|Claiming virtual lport ced5a54f-bfab-40b2-8c40-82c97f3c2586 for this chassis with the virtual parent cb15f805-943d-4efa-9646-7a700e6cd81b
```

So I wonder what's up with that. It seems that OVN is happy if there is an IP assigned to parent and the sub-ports via Neutron, but it doesn't like it when there is no IP assigned (and port security enabled?)