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

Bug 1643992

Summary:	Generating fencing from capitalized MAC returns nothing
Product:	Red Hat OpenStack	Reporter:	David Vallee Delisle <dvd>
Component:	openstack-tripleo-common	Assignee:	David Vallee Delisle <dvd>
Status:	CLOSED ERRATA	QA Contact:	Marian Krcmarik <mkrcmari>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	13.0 (Queens)	CC:	chjones, jslagle, marjones, mburns, michele, ojanas, pkomarov, slinaber
Target Milestone:	z5	Keywords:	Triaged, ZStream
Target Release:	13.0 (Queens)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-common-8.6.6-12.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-14 13:54:52 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 David Vallee Delisle 2018-10-29 16:59:30 UTC

Description of problem:
When deploying using instackenv.json with capitalized MAC, the ports are created with lower case. When we later generate fencing, nothing is returned

Version-Release number of selected component (if applicable):
All

How reproducible:
All the time

Steps to Reproduce:
* Use capitalized MACs in instackenv.json
* Deploy environment
* openstack overcloud generate fencing --ipmi-lanplus --ipmi-level administrator --output fencing.yaml instackenv.json

Actual results:
File is empty.

This is the port list after deployment:
+--------------------------------------+-------------------+
| UUID | Address |
+--------------------------------------+-------------------+
| dd295dab-c162-496f-ac67-da8e53587237 | f4:e9:d4:72:a7:2e |
| 0ae89236-e5b4-40bd-bc19-9cb4e7a224b5 | f4:e9:d4:72:a9:14 |
| 839443dd-6d54-4336-a751-8839294349a8 | f4:e9:d4:ed:fa:32 |
| 49bbe677-b958-4d1c-bfc0-49152eff4dcd | f4:e9:d4:ed:f9:90 |
| 5225e0fd-b37d-4dff-91f7-4817f724f10d | f4:e9:d4:72:a9:b6 |
+--------------------------------------+-------------------+

Expected results:
We should have a populated fencing.yaml file


Additional info:

Comment 26 Michele Baldessari 2019-03-07 11:50:59 UTC

*** Bug 1684119 has been marked as a duplicate of this bug. ***

Comment 28 errata-xmlrpc 2019-03-14 13:54:52 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/RHBA-2019:0448