Bug 1109079
Summary: | Packstack installation fail: restorecon not found | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Petr Matousek <pematous> | |
Component: | openstack-puppet-modules | Assignee: | Lukas Bezdicka <lbezdick> | |
Status: | CLOSED ERRATA | QA Contact: | Ido Ovadia <iovadia> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 5.0 (RHEL 6) | CC: | aortega, breeler, derekh, lars, lbezdick, mmagr, rharwood, termina, yeylon | |
Target Milestone: | rc | Keywords: | Triaged | |
Target Release: | 5.0 (RHEL 6) | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | openstack-puppet-modules-2014.1-14.4.el6ost | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1112372 (view as bug list) | Environment: | ||
Last Closed: | 2014-07-28 18:59:02 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: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1105094, 1108005, 1112372 |
Description
Petr Matousek
2014-06-13 08:21:37 UTC
Note: The issue is fixed, installation completed successfully, suggesting to move to verified. packages under tests: openstack-packstack-puppet-2014.1.1-0.24.dev1120.el6ost.noarch openstack-packstack-2014.1.1-0.24.dev1120.el6ost.noarch openstack-puppet-modules-2014.1-14.4.el6ost.noarch I am getting a similar error using packstack --allinone, how were you able to resolve this? Have all of the latest updates. Thanks! 10.0.0.213_swift.pp: [ ERROR ] Applying Puppet manifests [ ERROR ] ERROR : Error appeared during Puppet run: 10.0.0.213_swift.pp Error: /Stage[main]/Main/Swift::Storage::Loopback[swift_loopback]/Swift::Storage::Ext4[swift_loopback]/Swift::Storage::Mount[swift_loopback]/Exec[restorecon_mount_swift_loopback]: Failed to call refresh: Could not find command 'restorecon' You will find full trace in log /var/tmp/packstack/20140619-164551-2eLjEN/manifests/10.0.0.213_swift.pp.log Please check log file /var/tmp/packstack/20140619-164551-2eLjEN/openstack-setup.log for more information Hi, I guess you are reporting RDO issue, if this is only thing broken for you, you might workaround it by changing line in /usr/share/openstack-puppet/modules/swift/manifests/storage/mount.pp:68 path => ['/usr/sbin', '/bin'], to path => ['/usr/sbin', '/sbin'], And as for the package it should be hopefully out soon. (In reply to termina from comment #2) > I am getting a similar error using packstack --allinone, how were you able > to resolve this? Have all of the latest updates. > > Thanks! > > 10.0.0.213_swift.pp: [ ERROR ] > Applying Puppet manifests [ ERROR ] > > ERROR : Error appeared during Puppet run: 10.0.0.213_swift.pp > Error: > /Stage[main]/Main/Swift::Storage::Loopback[swift_loopback]/Swift::Storage:: > Ext4[swift_loopback]/Swift::Storage::Mount[swift_loopback]/ > Exec[restorecon_mount_swift_loopback]: Failed to call refresh: Could not > find command 'restorecon' > You will find full trace in log > /var/tmp/packstack/20140619-164551-2eLjEN/manifests/10.0.0.213_swift.pp.log > Please check log file > /var/tmp/packstack/20140619-164551-2eLjEN/openstack-setup.log for more > information (In reply to Lukas Bezdicka from comment #3) > Hi, I guess you are reporting RDO issue, if this is only thing broken for > you, you might workaround it by changing line in > /usr/share/openstack-puppet/modules/swift/manifests/storage/mount.pp:68 Yes, this exists in RDO and the fix you mention works there. *** Bug 1114100 has been marked as a duplicate of this bug. *** Verified ======== openstack-packstack-puppet-2014.1.1-0.35.dev1220.el6ost.noarch openstack-packstack-2014.1.1-0.35.dev1220.el6ost.noarch openstack-puppet-modules-2014.1-19.1.el6ost.noarch 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. http://rhn.redhat.com/errata/RHEA-2014-0950.html |