Bug 1386460 - can not install allinone ironic with RDO Newton version [NEEDINFO]
Summary: can not install allinone ironic with RDO Newton version
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: RDO
Classification: Community
Component: rdopkg
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: trunk
Assignee: Jakub Ruzicka
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-19 03:05 UTC by Benlei Xu
Modified: 2019-06-24 12:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-24 12:02:07 UTC
chris.brown: needinfo? (15201676659)


Attachments (Terms of Use)

Description Benlei Xu 2016-10-19 03:05:00 UTC
Description of problem:
The ironic.pp module have an error while i use rdo newton release to install allinone ironic service.

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

How reproducible:


Steps to Reproduce:
1.yum install -y centos-release-openstack-newton && yum update -y
2.yum install packstack && packstack --gen-answer-file=test.txt
3.modify test.txt and set CONFIG_IRONIC_INSTALL=y
4.packstack --answer-file=test.txt

Actual results:
It gives the below errors:
192.168.137.13_controller.pp:                     [ ERROR ]             
Applying Puppet manifests                         [ ERROR ]

ERROR : Error appeared during Puppet run: 192.168.137.13_controller.pp
Error: Syntax error at '{'; expected '}' at /var/tmp/packstack/9c2f83ef3b99486a94498061ae7bdf76/modules/packstack/manifests/ironic.pp:9 on node newton
You will find full trace in log /var/tmp/packstack/20161018-232249-2yB_CJ/manifests/192.168.137.13_controller.pp.log
Please check log file /var/tmp/packstack/20161018-232249-2yB_CJ/openstack-setup.log for more information

Expected results:
All the services i installed should be normal!

Additional info:

Comment 1 Christopher Brown 2017-06-22 15:22:00 UTC
Hi Benlei,

I'm just following up on this, can you confirm if this is still a problem?

Thanks


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