Bug 1643992 - Generating fencing from capitalized MAC returns nothing
Summary: Generating fencing from capitalized MAC returns nothing
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-common
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z5
: 13.0 (Queens)
Assignee: David Vallee Delisle
QA Contact: Marian Krcmarik
URL:
Whiteboard:
: 1684119 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-29 16:59 UTC by David Vallee Delisle
Modified: 2022-03-13 16:31 UTC (History)
8 users (show)

Fixed In Version: openstack-tripleo-common-8.6.6-12.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-14 13:54:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1800504 0 None None None 2018-10-29 16:59:29 UTC
OpenStack gerrit 625203 0 None MERGED Generating fencing for capitalized MACs 2020-11-06 15:34:31 UTC
Red Hat Issue Tracker OSP-13773 0 None Closed [ubi8:8.5-214] Need to fix vulnerabilities for rpm-libs(4.14.3-19.el8) package 2022-06-06 07:51:06 UTC
Red Hat Product Errata RHBA-2019:0448 0 None None None 2019-03-14 13:55:01 UTC

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


Note You need to log in before you can comment on or make changes to this bug.