Bug 1532610

Summary:	Upper case letters in HostnameFormat parameters cause trouble
Product:	Red Hat OpenStack	Reporter:	Michal Przybyl <michal.przybyl>
Component:	openstack-tripleo-heat-templates	Assignee:	Emilien Macchi <emacchi>
Status:	CLOSED ERRATA	QA Contact:	Gurenko Alex <agurenko>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	9.0 (Mitaka)	CC:	aschultz, emacchi, joflynn, mburns, rhel-osp-director-maint
Target Milestone:	zstream	Keywords:	Triaged, ZStream
Target Release:	9.0 (Mitaka)
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-2.0.0-63.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1532850 1532852 (view as bug list)		Environment:
Last Closed:	2018-07-05 12:26:25 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:
Bug Blocks:	1532850, 1532852

Description Michal Przybyl 2018-01-09 12:47:01 UTC

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 Michal Przybyl 2018-01-10 13:12:29 UTC

Hello,
May I ask why Target Release was changed from 8 to 9?

We are preparing update of our infrastructure from 8 to 10 and we will still hit this issue.

Regards

Comment 10 errata-xmlrpc 2018-07-05 12:26:25 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-2018:2140