other_config:vlan-limit is not purged by default

Bug #1982991 reported by Takashi Kajinami
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Won't Fix

Bug Description

Currently the vswitch::ovs class does not remove the vlan-limit option by default. Because of this, if a user once set the option and remove it later, the option is left unmanaged in openvswitch.

This is caused by the behavior of puppet and it does not sync the property when a nil value(undef) is passed.

description: updated
Changed in puppet-vswitch:
importance: Undecided → High
assignee: nobody → Takashi Kajinami (kajinamit)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to puppet-vswitch (master)
Changed in puppet-vswitch:
status: New → In Progress
Revision history for this message
Takashi Kajinami (kajinamit) wrote :

This was not actually a regression. We expected the change in yoga allows users to purge the config by default but that was not true.

While implementing this, I noticed that ovn-controller sets "0" automatically if the parameter is not set, and that is causing broken idempotency.

I'll give it another thought to find out any good way to handle this but I might just close this as WON'T FIX if I don't come up with any good solutions.

description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on puppet-vswitch (master)

Change abandoned by "Takashi Kajinami <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/puppet-vswitch/+/851283

Changed in puppet-vswitch:
assignee: Takashi Kajinami (kajinamit) → nobody
status: In Progress → Won't Fix
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.