Bug 1291345 - Syntax error at '{'; expected '}' at /etc/puppet/manifests/puppet-stack-config.pp:111
Summary: Syntax error at '{'; expected '}' at /etc/puppet/manifests/puppet-stack-confi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: instack-undercloud
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ga
: 8.0 (Liberty)
Assignee: Mike Burns
QA Contact: Raviv Bar-Tal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-14 16:07 UTC by wes hayutin
Modified: 2016-04-07 21:43 UTC (History)
4 users (show)

Fixed In Version: instack-undercloud-2.2.1-2.el7ost
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-07 21:43:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:0604 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 8 director Enhancement Advisory 2016-04-08 01:03:56 UTC

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


Note You need to log in before you can comment on or make changes to this bug.