Bug 1641790 - manage_vlans=[F|f]alse evaluates to True
Summary: manage_vlans=[F|f]alse evaluates to True
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-ansible
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: beta
: 14.0 (Rocky)
Assignee: Jakub Libosvar
QA Contact: Arkady Shtempler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-22 18:57 UTC by Dan Radez
Modified: 2019-01-11 11:54 UTC (History)
3 users (show)

Fixed In Version: python-networking-ansible-1.0.4-3.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-11 11:54:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 613568 0 None None None 2018-11-05 14:45:21 UTC
Red Hat Product Errata RHEA-2019:0045 0 None None None 2019-01-11 11:54:19 UTC

Description Dan Radez 2018-10-22 18:57:09 UTC 
Description of problem:
When passing the manage_vlans parameter to the switch configuration the functionality intended to be turned off stays on

Version-Release number of selected component (if applicable):
OSP 14 python-networking-ansible 1.0.4

How reproducible:
Everytime

Steps to Reproduce:
1. Deploy OSP 14 with Ironic in the overcloud and networking-ansible
2. do not permit the switch user to create vlans
3. deploy a baremetal guest

Actual results:
Error message stating no permission to create VLANs

Expected results:
No error, configuration successful


Additional info:
If I set manage_vlans='' then empty string resolves false and the functionality is disabled
Comment 5 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
Note You need to log in before you can comment on or make changes to this bug.