Bug 1532852

Summary: (ocata) Upper case letters in HostnameFormat parameters cause trouble
Product: Red Hat OpenStack Reporter: Emilien Macchi <emacchi>
Component: openstack-tripleo-heat-templatesAssignee: Emilien Macchi <emacchi>
Status: CLOSED EOL QA Contact: Gurenko Alex <agurenko>
Severity: medium Docs Contact:
Priority: medium    
Version: 11.0 (Ocata)CC: agurenko, emacchi, mburns, michal.przybyl, rhel-osp-director-maint
Target Milestone: asyncKeywords: Triaged, ZStream
Target Release: 11.0 (Ocata)   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1532610 Environment:
Last Closed: 2018-06-22 12:39:54 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: 1532610    
Bug Blocks: 1532850    

Description Emilien Macchi 2018-01-09 22:01:26 UTC 
+++ This bug was initially created as a clone of Bug #1532610 +++

Hello, 
Please backport solution suggested in:
https://access.redhat.com/support/cases/#/case/01988025


Description of problem:
Hello,
During out update process from OSP8 to OSP9 we hit problem with script:
/usr/share/openstack-tripleo-heat-templates/extraconfig/tasks/major_upgrade_pacemaker_migrations.sh
in if:
'if [ "$(hiera -c /etc/puppet/hiera.yaml bootstrap_nodeid)" = "$(facter hostname)" ]; then'
This is always false because:
hiera -c /etc/puppet/hiera.yaml bootstrap_nodeid
NCEOSPCTL0
and,
[root@nceospctl0 heat-config-script]# facter hostname
nceospctl0.

Because of that pacemaker update is never executed and upgrading failed.

We are using uppercase names in our deployment configuration:
parameter_defaults:
  ControllerHostnameFormat: 'NCEOSPCTL%index%'
  ComputeHostnameFormat: 'NCEOSPCPU%index%'
...
We noticed similar bug in different files :
https://bugzilla.redhat.com/show_bug.cgi?id=1382062

Have a nice day,
Michal

Where are you experiencing the behavior?  What environment?

OSP8 to OSP9 upgrade, expecting same on OSP9 to OSP10 upgrade.

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


How reproducible:
Just use capital letters in hostnames

Actual results:



Expected results:


Additional info:
Support case:
https://access.redhat.com/support/cases/#/case/01988025
Comment 1 Scott Lewis 2018-06-22 12:39:54 UTC 
OSP11 is now retired, see details at https://access.redhat.com/errata/product/191/ver=11/rhel---7/x86_64/RHBA-2018:1828