Bug 1368791 - Packstack fails at cinder.pp: when setting CONFIG_VCENTER_HOST.
Summary: Packstack fails at cinder.pp: when setting CONFIG_VCENTER_HOST.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-packstack
Version: 9.0 (Mitaka)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Ivan Chavero
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-21 12:21 UTC by Tzach Shefi
Modified: 2016-08-22 11:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-22 11:08:33 UTC
Target Upstream Version:


Attachments (Terms of Use)
packstack logs plus answer file mitaka.conf (5.29 MB, application/x-gzip)
2016-08-21 12:21 UTC, Tzach Shefi
no flags Details

Description Tzach Shefi 2016-08-21 12:21:01 UTC
Created attachment 1192581 [details]
packstack logs plus answer file mitaka.conf

Description of problem: While testing packstack with vmware/vcenter, I've updated a few parameters including CONFIG_VCENTER_HOST=10.35.163.44

Once I run Packstack it failed at cinder.pp, also clears parameter info from answer file. At first figured might have forgoten to set this param. On second attempt I updated and saved answer files, also greped to verify. Reran packstack only to hit same problem and see that answer file(mitaka.conf) parameter CONFIG_VCENTER_HOST= is yet again blank. 

 10.35.163.22_keystone.pp:                            [ DONE ]       
10.35.163.22_cinder.pp:                           [ ERROR ]         
Applying Puppet manifests                         [ ERROR ]

ERROR : Error appeared during Puppet run: 10.35.163.22_cinder.pp
Error: Could not find data item CONFIG_VCENTER_HOST in any Hiera data file and no default supplied at /var/tmp/packstack/e494a0f242544c809922ff2a832d1e69/manifests/10.35.163.22_cinder.pp:98 on node dhcp163-22.scl.lab.tlv.redhat.com
You will find full trace in log /var/tmp/packstack/20160821-145054-r6zwIS/manifests/10.35.163.22_cinder.pp.log
Please check log file /var/tmp/packstack/20160821-145054-r6zwIS/openstack-setup.log for more information

Version-Release number of selected component (if applicable):
RHEL7.2 
openstack-packstack-8.0.0-4.el7ost.noarch
openstack-packstack-puppet-8.0.0-4.el7ost.noarch
vmware 5.5u3

How reproducible:
Happened twice, as explained on description. 

Steps to Reproduce:
1. Fill in/Update answer file 
2. Packstack deploy hit cinder.pp error
3. Check answer file CONFIG_VCENTER_HOST= is empty again. 

Actual results:
Fails to complete Cinder.pp also clears CONFIG_VCENTER_HOST parameter. 

Expected results:
Should continue without errors. 

Additional info:
Attached logs and answer file (mitaka.conf), This should be/was set to  CONFIG_VCENTER_HOST=10.35.163.44 
Attached answer file is what it looks after hitting bug.  

# grep CONFIG_VCENTER_HOST mitaka.conf    (after first run)
CONFIG_VCENTER_HOST=
# vi mitaka.conf     (Re added address)
# grep CONFIG_VCENTER_HOST mitaka.conf    (Before packstack)
CONFIG_VCENTER_HOST=10.35.163.44
# packstack --debug --answer-file mitaka.conf
# grep CONFIG_VCENTER_HOST mitaka.conf    (after second run again no value set)
CONFIG_VCENTER_HOST=

Comment 2 Tzach Shefi 2016-08-22 11:08:33 UTC
Closing as not a bug, user error. 
After another attempt I found out that this parameter: 
CONFIG_VMWARE_BACKEND=   wasn't changed to y, or rather it was but I forgot to save it as such, guessing this is what caused  CONFIG_VCENTER_HOST= to be cleared again and again. 

After fixing it, Cinder.pp passed fine.


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