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

Bug 1678893

Summary:	[OSP 15][tripleo-heat-templates] - make uuid for hiera per-node customization case insensitive.
Product:	Red Hat OpenStack	Reporter:	Alex Schultz <aschultz>
Component:	openstack-tripleo-heat-templates	Assignee:	Alex Schultz <aschultz>
Status:	CLOSED ERRATA	QA Contact:	Sasha Smolyak <ssmolyak>
Severity:	high	Docs Contact:
Priority:	high
Version:	15.0 (Stein)	CC:	mburns
Target Milestone:	Upstream M3	Keywords:	Triaged
Target Release:	15.0 (Stein)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-10.3.1-0.20190314080339.05f1ae0.el8ost.noarch	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1678895 1678896 (view as bug list)		Environment:
Last Closed:	2019-09-21 11:20:27 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1678346, 1678895, 1678896, 1679767, 1679768, 1679769

Description Alex Schultz 2019-02-19 20:14:25 UTC

This bug was initially created as a copy of Bug #1678346

I am copying this bug because: 

This affects all versions OSP15 and below for per-node hiera customization for users who have upgraded or deployed with RHEL7.5 and used an uppercase system uuid for per-node hieradata customization or os-net-config mappings.


Description of problem:

This has been fixed for osp13+
https://bugzilla.redhat.com/show_bug.cgi?id=1668774
https://bugzilla.redhat.com/show_bug.cgi?id=1654449

OSP 10 needs a similar fix to assist where environments are being patched and run into issues when dmidecode is updated to >= 3.1.




Version-Release number of selected component (if applicable):
openstack-tripleo-heat-templates-5.3.10-23.el7ost.noarch

Comment 8 errata-xmlrpc 2019-09-21 11:20:27 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:2811