Bug 1678346

Summary: [OSP 10][tripleo-heat-templates] - make uuid for hiera per-node customization case insensitive.
Product: Red Hat OpenStack Reporter: Matt Flusche <mflusche>
Component: openstack-tripleo-heat-templatesAssignee: Alex Schultz <aschultz>
Status: CLOSED ERRATA QA Contact: Sasha Smolyak <ssmolyak>
Severity: high Docs Contact:
Priority: high    
Version: 10.0 (Newton)CC: aschultz, hrybacki, mburns, mgeary
Target Milestone: ---Keywords: Triaged, ZStream
Target Release: 10.0 (Newton)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-5.3.10-25.el7ost Doc Type: Bug Fix
Doc Text:
Previously, when you upgraded to RHEL 7.6, you introduced a new version of dmidecode that represents system UUIDs in lowercase characters. This change of case affected per-node hierdata customization for systems that relied on uppercase UUIDs. With this update, you can use either uppercase or lowercase UUIDs for per-node customizations. The recommendation is to use lowercase.
 Story Points: ---
Clone Of:
: 1679767 1679768 (view as bug list) Environment:
Last Closed: 2019-04-30 16:58: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:
Bug Depends On: 1678893, 1678895, 1678896    
Bug Blocks: 1679767, 1679768, 1679769    

Description Matt Flusche 2019-02-18 15:02:20 UTC 
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 6 Harry Rybacki 2019-02-27 19:43:15 UTC 
I picked up the change while creating a build for RHBZ#167498. Updating FIV to note as much.
Comment 16 errata-xmlrpc 2019-04-30 16:58: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:0921