Bug 1633193

Summary: Specyfing undercloud_ntp_servers results in corrupted hieradata
Product: Red Hat OpenStack Reporter: Michal Pryc <mpryc>
Component: instack-undercloudAssignee: James Slagle <jslagle>
Status: CLOSED ERRATA QA Contact: Arik Chernetsky <achernet>
Severity: medium Docs Contact:
Priority: medium    
Version: 10.0 (Newton)CC: aschultz, jschluet, mariel, mburns
Target Milestone: z4Keywords: Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: instack-undercloud-8.4.6-4.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1651692 (view as bug list) Environment:
Last Closed: 2019-01-16 17:55:03 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: 1651692    

Description Michal Pryc 2018-09-26 11:56:14 UTC
Description of problem:

This was observed on OSP10 (Newton) together with RHEL 7.4.

Running "openstack undercloud install" with the following values in undercloud.conf:

 undercloud_ntp_servers = clock.redhat.com

Results hieradata to contain improper value for ntp::servers: as follows:

   ntp::servers: [&#x27;clock.test.com&#x27;]


It's because this value is in double curly brackets {{ }}, however according to MUSTACHE(5):

"
All variables are HTML escaped by default. If you want to return unescaped HTML, use the triple curling brackets: {{{name}}}.
"

Correcting puppet-stack-config.yaml.template to include triple curly brackets fixes the problem:

ntp::servers: ['clock.test.com']

Passing list of undercloud_ntp_servers in the undercloud.conf with corrected template results in:

ntp::servers: ['clock.test.com','secondclock.test.com']

Comment 15 errata-xmlrpc 2019-01-16 17:55:03 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:0068