Bug 950066

Summary:	Could not evaluate: undefined method `[]=' for nil:NilClass
Product:	[Fedora] Fedora EPEL	Reporter:	Sandro Mathys <sandro>
Component:	puppet	Assignee:	Jeroen van Meeuwen <vanmeeuwen+fedora>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	el6	CC:	dcleal, jose.p.oliveira.oss, k.georgiou, ktdreyer, mastahnke, moses, tmz, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-04-09 15:17:33 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 Sandro Mathys 2013-04-09 14:45:26 UTC

Description of problem:
Running Packstack (openstack-packstack) with the latest Puppet fails with "Could not evaluate: undefined method `[]=' for nil:NilClass". Downgrading Puppet fixes this issue.

Version-Release number of selected component (if applicable):
puppet-2.6.18-2.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. yum install --enablerepo=epel-testing -y puppet openstack-packstack
2. packstack --gen-answer-file=/tmp/ans.txt
3. packstack --answer-file=/tmp/ans.txt

(to making testing easier, editing the ans.txt to suit the test system better shouldn't change the result unless you disable most or all of the OpenStack components)
 
Actual results:
ERROR : Error during puppet run : err: /Stage[main]/Keystone/Service[keystone]: Could not evaluate: undefined method `[]=' for nil:NilClass

(According to other reports the issue can also show up in other manifests, either due to different Packstack versions or different configuration (ans.txt)).


Expected results:
 **** Installation completed successfully ******

Additional info:

Comment 1 Dominic Cleal 2013-04-09 15:17:33 UTC


*** This bug has been marked as a duplicate of bug 908655 ***