If data-port or bridge-mappings are incorrect this should be reflected in workload status

Bug #1872799 reported by David Ames
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Neutron Gateway Charm
Triaged
Wishlist
Unassigned
OpenStack Neutron Open vSwitch Charm
Triaged
Wishlist
Unassigned

Bug Description

If data-port or bridge-mappings are incorrect, it would be very helpful to report this in workload status.

If data-port is set to an interface name and that is not present it will error out, but if it is set to mac addresses even when there is no match the charm gives no indication there is a problem.

This can lead to very difficult to debug scenarios where some but not all FIPs or virtual router interfaces are not accessible.

Changed in charm-neutron-gateway:
status: New → Triaged
Changed in charm-neutron-openvswitch:
status: New → Triaged
Changed in charm-neutron-gateway:
importance: Undecided → Wishlist
Changed in charm-neutron-openvswitch:
importance: Undecided → Wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.