vs_bridge is not idempotent when external_ids is set
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
puppet-vswitch |
Fix Released
|
Critical
|
Takashi Kajinami |
Bug Description
When a vs_bridge resource is defined with external_ids, the second run detects the change even with the same manifest.
On the other hand, the third run exists without any change detected.
$ cat test.pp
vs_bridge { 'test':
ensure => present,
external_ids => 'bridge-id=test'
}
$ sudo puppet apply test.pp
Notice: Compiled catalog for undercloud-
Notice: /Stage[
Notice: Applied catalog in 0.99 seconds
$ sudo puppet apply test.pp
Notice: Compiled catalog for undercloud-
Notice: /Stage[
Notice: Applied catalog in 0.62 seconds
$ sudo puppet apply test.pp
Notice: Compiled catalog for undercloud-
Notice: Applied catalog in 0.61 seconds
Changed in puppet-vswitch: | |
assignee: | nobody → Takashi Kajinami (kajinamit) |
I confirmed the external-id is not set after the first run,
$ sudo puppet apply test.pp 0.redhat. local in environment production in 0.21 seconds main]/Main/ Vs_bridge[ test]/ensure: created
Notice: Compiled catalog for undercloud-
Notice: /Stage[
Notice: Applied catalog in 0.63 seconds
$ sudo ovs-vsctl br-get-external-id test
$
but it is set after the second run so the issue is specific to the initial creation.
$ $ sudo puppet apply test.pp 0.redhat. local in environment production in 0.22 seconds main]/Main/ Vs_bridge[ test]/external_ ids: external_ids changed '' to 'bridge-id=test'
Notice: Compiled catalog for undercloud-
Notice: /Stage[
Notice: Applied catalog in 0.64 seconds
$ sudo ovs-vsctl br-get-external-id test
bridge-id=test