Bug 1011628
| Summary: | packstack reports installation completed successfully but nothing installed | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Community] RDO | Reporter: | Robin Goldstone <goldstone1> | ||||
| Component: | openstack-packstack | Assignee: | Ivan Chavero <ichavero> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | yeylon <yeylon> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | unspecified | CC: | aortega, derekh, goldstone1, markmc, mmagr, srevivo, yeylon | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | openstack-packstack-2013.2.1-0.36.dev1013.el6.noarch | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-03-30 23:04:31 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: | |||||||
| Attachments: |
|
||||||
|
Description
Robin Goldstone
2013-09-24 16:26:49 UTC
Robin, can you please attach the log file from packstack to the bugzilla? And can you include in a comment the RDO discussion thread where you originally reported this issue? This is weird, the only way how packstack won't fail without puppet is that the puppet installation (yum install -y puppet) failed but reported success Or puppet RPM is installed but manually deleted, so Packstack thinks it is installed. Hi Perry, I reported this to the RDO forum here: http://openstack.redhat.com/forum/discussion/512/rdo-install-completes-successfully-but-does-nothing/p1 Note when I initially tried the install, my system did not have the EPEL repository set up in yum, which they speculated might be the issue. However, this time around I have EPEL properly configured. Here is the openstack log file. It is short so I am putting it inline. # brutus2 /var/tmp/packstack/20130923-155141-gIO2zs > cat openstack-setup.log 2013-09-23 15:51:41::INFO::run_setup::399::root:: A new answerfile was created in: /root/packstack-answers-20130923-155141.txt 2013-09-23 15:51:41::INFO::run_setup::359::root:: Comparing pre- conditions, value: 'yes', and match: 'yes' 2013-09-23 15:51:41::INFO::run_setup::359::root:: Comparing pre- conditions, value: 'yes', and match: 'yes' 2013-09-23 15:51:41::INFO::run_setup::359::root:: Comparing pre- conditions, value: 'yes', and match: 'yes' 2013-09-23 15:51:41::INFO::run_setup::359::root:: Comparing pre- conditions, value: 'y', and match: 'y' 2013-09-23 15:51:41::INFO::run_setup::359::root:: Comparing pre- conditions, value: 'yes', and match: 'yes' 2013-09-23 15:51:41::INFO::run_setup::359::root:: Comparing pre- conditions, value: 'y', and match: 'y' 2013-09-23 15:51:41::INFO::run_setup::359::root:: Comparing pre- conditions, value: 'y', and match: 'y' 2013-09-23 15:51:41::INFO::run_setup::359::root:: Comparing pre- conditions, value: 'True', and match: 'True' 2013-09-23 15:51:41::INFO::run_setup::359::root:: Comparing pre- conditions, value: 'y', and match: 'y' 2013-09-23 15:51:41::INFO::run_setup::359::root:: Comparing pre- conditions, value: 'True', and match: 'True' 2013-09-23 15:51:41::INFO::run_setup::359::root:: Comparing pre- conditions, value: 'n', and match: 'y' 2013-09-23 15:51:41::INFO::run_setup::359::root:: Comparing pre- conditions, value: 'False', and match: 'True' 2013-09-23 15:51:41::INFO::run_setup::359::root:: Comparing pre- conditions, value: 'False', and match: 'True' 2013-09-23 15:51:41::INFO::run_setup::359::root:: Comparing pre- conditions, value: 'y', and match: 'y' 2013-09-23 15:51:41::INFO::run_setup::359::root:: Comparing pre- conditions, value: 'y', and match: 'y' 2013-09-23 15:51:41::INFO::run_setup::359::root:: Comparing pre- conditions, value: 'n', and match: 'y' 2013-09-23 15:51:41::INFO::run_setup::359::root:: Comparing pre- conditions, value: 'y', and match: 'y' 2013-09-23 15:51:41::INFO::run_setup::359::root:: Comparing pre- conditions, value: 'False', and match: 'True' 2013-09-23 15:51:41::INFO::run_setup::359::root:: Comparing pre- conditions, value: 'False', and match: 'True' 2013-09-23 15:51:41::INFO::run_setup::359::root:: Comparing pre- conditions, value: 'False', and match: 'True' 2013-09-23 15:51:41::INFO::run_setup::359::root:: Comparing pre- conditions, value: 'yes', and match: 'yes' 2013-09-23 15:51:41::INFO::run_setup::359::root:: Comparing pre- conditions, value: 'yes', and match: 'yes' 2013-09-23 15:51:41::INFO::run_setup::359::root:: Comparing pre- conditions, value: 'False', and match: 'True' 2013-09-23 15:51:41::INFO::run_setup::359::root:: Comparing pre- conditions, value: 'False', and match: 'True' 2013-09-23 15:51:41::INFO::run_setup::359::root:: Comparing pre- conditions, value: 'y', and match: 'y' 2013-09-23 15:51:41::INFO::run_setup::359::root:: Comparing pre- conditions, value: 'yes', and match: 'yes' 2013-09-23 15:51:41::INFO::run_setup::359::root:: Comparing pre- conditions, value: 'yes', and match: 'yes' 2013-09-23 15:52:04::INFO::run_setup::598::root:: Removing /var/tmp/packstack/7eddf76994114d0083a875ed5b7b699f on 192.168.95.35 (if it is a remote host) 2013-09-23 15:52:04::INFO::run_setup::532::root:: * A new answerfile was created in: /root/packstack-answers-20130923-155141.txt 2013-09-23 15:52:04::INFO::run_setup::532::root:: * Time synchronization installation was skipped. Please note that unsynchronized time on server instances might be problem for some OpenStack components. 2013-09-23 15:52:04::INFO::run_setup::532::root:: * Did not create a cinder volume group, one already existed 2013-09-23 15:52:04::INFO::run_setup::532::root:: * To use the command line tools you need to source the file /root/keystonerc_admin created on 192.168.95.35 2013-09-23 15:52:04::INFO::run_setup::532::root:: * To use the console, browse to http://192.168.95.35/dashboard 2013-09-23 15:52:04::INFO::run_setup::532::root:: * To use Nagios, browse to http://192.168.95.35/nagios username : nagiosadmin, password : 7fb16e4ee14c4c66 2013-09-23 15:52:04::INFO::run_setup::532::root:: * The installation log file is available at: /var/tmp/packstack/20130923-155141-gIO2zs/openstack-setup.log # brutus2 /var/tmp/packstack/20130923-155141-gIO2zs > Hi Martin, puppet has never been installed on this system. Note we are not running "vanilla" RHEL but rather a customized distribution. We maintain our own repo and do not pull from public RHEL repos with the exception of EPEL, which I have set up for this project. It appears that puppet is available in the EPEL repo so packstack should be able to install it: # brutus2 /var/tmp/packstack/20130923-155141-gIO2zs > yum list puppet Loaded plugins: changelog, priorities, ps, refresh-packagekit, security 73 packages excluded due to repository priority protections Available Packages puppet.noarch 2.6.18-3.el6 epel # brutus2 /var/tmp/packstack/20130923-155141-gIO2zs > I can try the manual yum install of puppet if you want. -Robin It would be more useful if you would run packstack with --debug switch and attach tarball of /var/tmp/packstack to this bug. Created attachment 802417 [details]
logs from debug packstack installation
OK here is some progress. Per discussion on my other bugzilla, I am now pointing to our RHEL satellite in addition to TOSS. I am now getting MUCH farther (but still failing, see below) including successful installation of puppet. One thing in particular I noted is that the step: Installing Dependencies... [ DONE ] took a lot longer than it has in the past. It seems like potentially when I didn't include the RHEL repo, this step was not successfully installing all the dependencies yet it seemingly completed with a successful return code. So that might be something to look at. However, as I stated in my original post to the RDO forum, even if packstack didn't detect that the puppet installation had failed, it should still fail when it tries to run puppet, since any invocation of puppet would fail. So it does not seem like you are checking return codes on every command you run. That is just my $0.02. As mentioned above, I am now getting farther but still failing. The reason is it tried to install qemu-kvm but failed because we have our own modified version of this RPM: # brutus3 /root > rpm -q qemu-kvm package qemu-kvm is not installed # brutus3 /root > rpm -qa|grep qemu-kvm qemu-kvm-rhev-0.12.1.2-2.355.ch5.1.x86_64 I need to figure out how to resolve this conflict. But clearly having access to the RHEL repo made things work better. It is just a question of why packstack didn't report any errors when it couldn't install puppet. Regards, Robin Tested and this problem does not appear anymore:
Removed puppet:
yum erase -y puppet
packstack -d --answer-file=packstack-answers-20140428-194248.txt
...
Adding Nagios host manifest entries [ DONE ]
Adding post install manifest entries [ DONE ]
Preparing servers [ DONE ]
Installing Dependencies [ ERROR ]
ERROR : Failed to run remote script, stdout: no package provides puppet
Loaded plugins: product-id, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package puppet.noarch 0:3.5.1-1.el6 will be installed
--> Processing Dependency: facter >= 1:1.7.0 for package: puppet-3.5.1-1.el6.noarch
--> Processing Dependency: hiera >= 1.0.0 for package: puppet-3.5.1-1.el6.noarch
--> Processing Dependency: ruby-rgen >= 0.6.5 for package: puppet-3.5.1-1.el6.noarch
--> Processing Dependency: rubygem-json for package: puppet-3.5.1-1.el6.noarch
--> Running transaction check
---> Package facter.x86_64 0:1.6.18-3.el6 will be updated
---> Package facter.x86_64 1:2.0.1-1.el6 will be an update
---> Package hiera.noarch 0:1.3.2-1.el6 will be installed
---> Package ruby-rgen.noarch 0:0.6.5-2.el6 will be installed
---> Package rubygem-json.x86_64 0:1.5.5-1.el6 will be installed
--> Processing Dependency: rubygems for package: rubygem-json-1.5.5-1.el6.x86_64
--> Finished Dependency Resolution
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
stderr: Warning: Permanently added '192.168.100.210' (RSA) to the list of known hosts.
+ trap t ERR
+ rpm -q --whatprovides puppet
+ yum install -y puppet
Error: Package: rubygem-json-1.5.5-1.el6.x86_64 (puppetlabs-deps)
Requires: rubygems
++ t
++ exit 1
|