Bug 1114121
| Summary: | openstack-packstack: packstack --allinone results in error. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Alexander Chuzhoy <sasha> | ||||||
| Component: | openstack-packstack | Assignee: | Lukas Bezdicka <lbezdick> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Ami Jeain <ajeain> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 5.0 (RHEL 7) | CC: | adahms, aortega, derekh, ichavero, lbezdick, sasha, sgordon, yeylon | ||||||
| Target Milestone: | rc | Keywords: | Unconfirmed | ||||||
| Target Release: | 5.0 (RHEL 7) | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | openstack-packstack-2014.1.1-0.30.dev1204.el7ost | Doc Type: | Bug Fix | ||||||
| Doc Text: |
Previously, there was a race condition when shutting down the firewalld service and starting the iptables service. While it was intended that shutting down the firewalld service before calling the puppet firewall class would resolve this issue, puppet resource ordering with before does not work with classes. Now, the puppet iptables service is used for ordering, making it possible to shut down the firewalld service and start the iptables service successfully under these conditions.
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-07-08 15:39:45 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: |
|
||||||||
Note: this doesn't occur for me or Toure. It's very strange. It's not 100% of the time. Hi Sasha, Is /var/tmp/packstack/20140627-144217-Z0WiwI/openstack-setup.log available somewhere? Thanks, Steve We are hitting this issue from time to time too, unfortunately we don't have reproducer or idea what's the cause. Sometimes iptables service fails first time. Workaround is to rerun packstack. Second time iptables service will start without problem. (In reply to Martin Magr from comment #4) > Second time iptables service will start without problem. Ugly, but I'll say it: what about Packstack re-trying this operation 2nd time before giving up? I tried it several times on 2 separated machines in different geographic locations and it re-occured 100%. Comparing the installation script between setup where it worked and mine didn't reveal what could be the issue. Re-running packstack resulted in successful deployment. attaching the file /var/tmp/packstack/20140627-144217-Z0WiwI/openstack-setup.log Created attachment 913427 [details]
/var/tmp/packstack/20140627-144217-Z0WiwI/openstack-setup.log
Hi Lukas, This bug is marked for inclusion in RHEA-2014:18169-01 [1] but does not currently contain draft documentation text. To ensure the timely release of this advisory please provide draft documentation text for this bug as soon as possible. If you do not think this bug requires errata documentation, set the requires_doc_text flag to "-". To add draft documentation text: * Select the documentation type from the "Doc Type" drop down field. * A template will be provided in the "Doc Text" field based on the "Doc Type" value selected. Enter draft text in the "Doc Text" field. For further information on this process refer to "Describing Errata Release and Technical Notes for Engineers" [2]. Thank you for your assistance! Kind regards, Andrew [1] https://errata.devel.redhat.com/docs/doc_text_info/18169 [2] https://engineering.redhat.com/docs/en-US/Policy/70.ecs/html/Describing_Errata_Release_and_Technical_Notes_for_Engineers/index.html 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-0846.html |
Created attachment 912939 [details] kickstart file. openstack-packstack: packstack --allinone results in error. Environment: openstack-packstack-puppet-2014.1.1-0.28.dev1194.el7ost.noarch iptables-1.4.21-13.el7.x86_64 openstack-packstack-2014.1.1-0.28.dev1194.el7ost.noarch openstack-selinux-0.5.5-3.el7ost.noarch openstack-puppet-modules-2014.1-18.el7ost.noarch Steps to reproduce: 1. Install RHEL 7.0 2. fix yum repos and run: yum install -y openstack-packstack 3. packstack --allinone Results: The deployment ends with: Applying 10.8.30.117_prescript.pp 10.8.30.117_prescript.pp: [ ERROR ] Applying Puppet manifests [ ERROR ] ERROR : Error appeared during Puppet run: 10.8.30.117_prescript.pp Error: Could not start Service[iptables]: Execution of '/sbin/service iptables start' returned 1: You will find full trace in log /var/tmp/packstack/20140627-144217-Z0WiwI/manifests/10.8.30.117_prescript.pp.log Please check log file /var/tmp/packstack/20140627-144217-Z0WiwI/openstack-setup.log for more information Also attaching the kickstart file describing the installation.