Ansible Networking feature is using “ansible” user to configure switch remotely via SSH. This “ansible” user is not permitted to create or delete VLANs on the switch and that’s fine, but sometimes we are trying to use this user for such purposes. There is a parameter called “manage_vlans” which is managed to be set to True/False we could add to “neutron-ml2-ansible.yaml” template prevent this “ansible” user to manage VLANs. The problem is that adding will cause the deployment to fail and we have to fix that.
*** This bug has been marked as a duplicate of bug 1641963 ***
This should be addressed by upstream: https://review.openstack.org/#/c/611297/ once it makes its way through the process.
Still need upstream backport to stable/rocky for https://review.openstack.org/#/c/611297/
> Still need upstream backport to stable/rocky Never mind its done, updated trackers.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:0045