OVS bridges and ports are not marked as managed by the charm
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Neutron Open vSwitch Charm |
Fix Released
|
Undecided
|
Przemyslaw Lal |
Bug Description
There's an inconsistent behaviour between neutron-openvswtich and neutron-gateway charms in marking OVS bridges and ports as managed by the charm.
The neutron-gateway charm sets `external_ids` to `{charm-
$ juju ssh neutron-gateway/2 sudo ovs-vsctl get bridge br-data external_ids
{charm-
$ juju ssh neutron-gateway/2 sudo ovs-vsctl get bridge br-int external_ids
{charm-
$ juju ssh neutron-gateway/2 sudo ovs-vsctl get interface ens7 external_ids master
{charm-
This behaviour allows the operator to determine which interfaces are managed by the charm and enables further work towards fully managed bridges and ports as discussed in related bug reports [0] and [1].
However, despite very similar configuration options and functionality, this behaviour is currently missing in the neutron-openvswitch charm:
$ juju ssh neutron-
{}
$ juju ssh neutron-
{}
$ juju ssh neutron-
{}
The expected behaviour would be that the neutron-openvswitch charm populates `external_ids` for all bridges and ports that it has configured, e.g.:
$ juju ssh neutron-
{charm-
$ juju ssh neutron-
{charm-
$ juju ssh neutron-
{charm-
The solution would be to replicate functionality implemented for charm-neutron-
[0] https:/
[1] https:/
[2] https:/
Changed in charm-neutron-openvswitch: | |
assignee: | nobody → Przemysław Lal (przemeklal) |
status: | New → In Progress |
Changed in charm-neutron-openvswitch: | |
milestone: | none → 21.04 |
Changed in charm-neutron-openvswitch: | |
status: | Fix Committed → Fix Released |
Patch available for review: https:/ /review. opendev. org/c/openstack /charm- neutron- openvswitch/ +/778458/