trying to set non-exists port down

Bug #1896913 reported by Robert Gildein
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
charm-ovn-chassis
Triaged
Wishlist
Robert Gildein

Bug Description

When changing the ``bridge-interface-mappings`` configuration from a non-existent interface to an existing one, you need to run the resolved twice. This is due to error when ``charm-helpers`` try to set a non-existent port down in the first resolved.

Example:
 1. the openstack-base bundle comes with a default ``eno2`` interface
 2. change the interface to valid (e.g. ``ens7``, the attached shell script changes to a list of MAC addresses)
 3. run ``juju resolved ovn-chassis/0``
  - ends in an error while running ``ip link set eno2 down``
 4. run ``juju resolved ovn-chassis/0``
  - resolved it

A shell script is attached to re-create the situation.

Revision history for this message
Robert Gildein (rgildein) wrote :
Frode Nordahl (fnordahl)
Changed in charm-ovn-chassis:
status: New → Triaged
importance: Undecided → Wishlist
Revision history for this message
Frode Nordahl (fnordahl) wrote :

This is basically bug by bug compatibility with the neutron-openvswitch and neutron-gateway charms.

The issue is similar to bug 1872799 but not quite the same as OVN allows you to get DVR-like functionality without having bridge mappings configured for all units.

The charm could definitively give more friendly feedback than going into a hook error for non-existing ports, and it would also be useful to update the workload message with information about chassis being configured for use as a gateway or not.

Changed in charm-ovn-chassis:
assignee: nobody → Robert Gildein (rgildein)
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.