Bug 1642004 - Ansible Networking – avoid “Switch configuration conflict” by including “Clean” step in deployment
Summary: Ansible Networking – avoid “Switch configuration conflict” by including “Clea...
Keywords:
Status: CLOSED DUPLICATE of bug 1641963
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-ansible
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Dan Radez
QA Contact: Arkady Shtempler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-23 11:14 UTC by Arkady Shtempler
Modified: 2018-10-23 14:50 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-23 14:50:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.