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

Bug 2026737

Summary:	When customer specify an uppercase mac address in fencing.yaml, fencing isn't configured for those nodes
Product:	Red Hat OpenStack	Reporter:	David Hill <dhill>
Component:	openstack-tripleo-heat-templates	Assignee:	OSP Team <rhos-maint>
Status:	CLOSED WONTFIX	QA Contact:	Joe H. Rahme <jhakimra>
Severity:	low	Docs Contact:
Priority:	low
Version:	16.2 (Train)	CC:	lmiccini, mburns
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	x86_64
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-03-09 14:06:39 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 Hill 2021-11-25 16:55:37 UTC

Description of problem:
When customer specify an uppercase mac address in fencing.yaml, fencing isn't configured for those nodes .   If customer modify fencing.yaml to use lowercase instead, fencing is properly configured.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 4 Luca Miccini 2023-03-09 14:06:39 UTC

fencing requires valid mac addresses to be specified in the respective templates. in case the nodes are already deployed "generate fencing" should be able to fetch the required mac automatically, otherwise there is no way to predict w/e a mac address is valid or not.
Documentation contains warnings and disclaimers about this so we feel like this doesn't warrant further investment.