Order of Netplan YAML definitions for OVS

[John Torquato]

I am reporting this bug at the recommendation of Lukas Märdian.

While attempting to apply the configuration of an Open vSwitch bridge including a fake bridge and a bond with 2 physical interfaces, I encountered the following error:

 /etc/netplan/ovsbr0_bad_def_order.yaml:26:13: Error in network definition: duplicate map entry 'lacp-time'
            lacp-time: fast
            ^
The associated YAML file “ovsbr0_bad_def_order.yaml” is included in the attached “ovsbr0_info.zip”.

Lukas reproduced the bug in his test environment, as well as provided a work-around.
According to Lukas, there appears to be a bug in the multi-pass processing of the input file “ovsbr0_bad_def_order.yaml” that was due to the ordering of YAML definitions.

The work-around is represented by the re-ordering in “ovsbr0_good_def_order.yaml” that is also found in attached “ovsbr0_info.zip”. I am happy to report that the work-around does indeed enable the bridge to be properly setup. I have also included various other files with bridge and port information extracted from the OVS DB.

Thanks in advance for your assistance in following-up with a permanent fix.

[Lukas Märdian (slyon)]

This is a multipass processing issue. "lacp-time" is added to the GHashTable on the first pass. If a 2nd pass is required (due to unknown interface definitions, caused by the YAML ordering) it will try to add "lacp-time" (or any other value) again to the HashTable, throwing this error.

A work around is, as described above, to have all interface definitions defined before/above the interface defining the "other-config".