Bug 1291345

Summary: Syntax error at '{'; expected '}' at /etc/puppet/manifests/puppet-stack-config.pp:111
Product: Red Hat OpenStack Reporter: wes hayutin <whayutin>
Component: instack-undercloudAssignee: Mike Burns <mburns>
Status: CLOSED ERRATA QA Contact: Raviv Bar-Tal <rbartal>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.0 (Liberty)CC: achernet, mburns, rhel-osp-director-maint, sasha
Target Milestone: gaKeywords: Automation, Triaged
Target Release: 8.0 (Liberty)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: instack-undercloud-2.2.1-2.el7ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-07 21:43: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:

Description wes hayutin 2015-12-14 16:07:49 UTC
Description of problem:

+ puppet apply --detailed-exitcodes /etc/puppet/manifests/puppet-stack-config.pp
[1;31mError: Could not parse for environment production: Syntax error at '{'; expected '}' at /etc/puppet/manifests/puppet-stack-config.pp:111 on node host15.beaker.tripleo.lab.eng.rdu2.redhat.com[0m
[1;31mError: Could not parse for environment production: Syntax error at '{'; expected '}' at /etc/puppet/manifests/puppet-stack-config.pp:111 on node host15.beaker.tripleo.lab.eng.rdu2.redhat.com[0m
+ rc=1
+ set -e
+ echo 'puppet apply exited with exit code 1'
puppet apply exited with exit code 1
+ '[' 1 '!=' 2 -a 1 '!=' 0 ']'
+ exit 1

Comment 3 Mike Burns 2015-12-14 16:21:15 UTC
Looks like a bad backport of https://review.openstack.org/#/c/221885/

Comment 6 Raviv Bar-Tal 2016-03-03 08:46:29 UTC
Automation pass for this puddle

Comment 8 errata-xmlrpc 2016-04-07 21:43: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://rhn.redhat.com/errata/RHEA-2016-0604.html