RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1085222 - Missing dependency on iptables-services package
Summary: Missing dependency on iptables-services package
Keywords:
Status: CLOSED DUPLICATE of bug 1038255
Alias: None
Product: RDO
Classification: Community
Component: openstack-packstack
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact: Ami Jeain
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-08 07:00 UTC by Jakub Libosvar
Modified: 2014-04-08 14:16 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-04-08 14:16:17 UTC
Embargoed:


Attachments (Terms of Use)
prescript.pp (584 bytes, text/plain)
2014-04-08 07:00 UTC, Jakub Libosvar
no flags Details

Description Jakub Libosvar 2014-04-08 07:00:25 UTC
Created attachment 883915 [details]
prescript.pp

Description of problem:
When deploying OS with Packstack on F20 that doesn't have package iptables-services installed, installation fails on "service iptables start".

Version-Release number of selected component (if applicable):
openstack-packstack-2014.1.1-0.8.dev1045.fc21.noarch

How reproducible:
Always

Steps to Reproduce:
1. Have F20 without iptables-services package
2. packstack --allinone
3.

Actual results:
prescript.pp fails

Expected results:


Additional info:
Installing iptables-services and reruning packstack fixed the problem. There is no explicit call for "service iptables start" in prescript.pp

^[[1;31mError: Could not start Service[iptables]: Execution of '/sbin/service iptables start' returned 6: ^[[0m
^[[1;31mError: /Stage[main]/Firewall::Linux::Redhat/Service[iptables]/ensure: change from stopped to running failed: Could not start Service[iptables]: Execution of '/sbin/service iptables start' returned 6: ^[[0m

Comment 1 Jakub Libosvar 2014-04-08 14:16:17 UTC

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


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