Bug 1642005

Summary:	Ansible Networking – Overcloud deployment fails if “manage_vlans” parameter is used
Product:	Red Hat OpenStack	Reporter:	Arkady Shtempler <ashtempl>
Component:	puppet-neutron	Assignee:	Dan Radez <dradez>
Status:	CLOSED ERRATA	QA Contact:	Arkady Shtempler <ashtempl>
Severity:	high	Docs Contact:
Priority:	high
Version:	14.0 (Rocky)	CC:	bfournie, jjoyce, jlibosva, jschluet, michapma, slinaber, tvignaud
Target Milestone:	beta	Keywords:	Reopened, Triaged
Target Release:	14.0 (Rocky)
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	puppet-neutron-13.3.1-0.20181013115834.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-11 11:54:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Arkady Shtempler 2018-10-23 11:15:29 UTC

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.

Comment 1 Bob Fournier 2018-10-23 14:48:56 UTC


*** This bug has been marked as a duplicate of bug 1641963 ***

Comment 2 Dan Radez 2018-10-23 15:00:34 UTC

This should be addressed by upstream:
https://review.openstack.org/#/c/611297/ once it makes its way through the process.

Comment 3 Bob Fournier 2018-11-08 19:57:59 UTC

Still need upstream backport to stable/rocky for https://review.openstack.org/#/c/611297/

Comment 4 Bob Fournier 2018-11-08 20:00:58 UTC

> Still need upstream backport to stable/rocky

Never mind its done, updated trackers.

Comment 9 errata-xmlrpc 2019-01-11 11:54:09 UTC

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