Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1642004

Summary:	Ansible Networking – avoid “Switch configuration conflict” by including “Clean” step in deployment
Product:	Red Hat OpenStack	Reporter:	Arkady Shtempler <ashtempl>
Component:	python-networking-ansible	Assignee:	Dan Radez <dradez>
Status:	CLOSED DUPLICATE	QA Contact:	Arkady Shtempler <ashtempl>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	14.0 (Rocky)	CC:	bfournie, jlibosva, michapma
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-23 14:50:25 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:14:05 UTC

Description of problem:

We have to include “Clean” procedure to our deployment in order to prevent switch configuration conflict.
For example, when Switch’s ports connected to BM Guests are already associated to some VLAN (on previous installation), we’ll have the configuration conflict on next time deployment, means that Ansible Runner won’t be able to override the existing configuration.

Comment 1 Bob Fournier 2018-10-23 14:50:25 UTC


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