Packstack fails starting iptables service

Bug #1305256 reported by Lars Kellogg-Stedman on 2014-04-09
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Packstack
Undecided
Unassigned

Bug Description

This bug is against packstack master (d7a5019e1ef43eb8d43bc2aff36e92b69a919027).

Running packstack on centos 6 fails early in the process with the following error:

ERROR : Error appeared during Puppet run: 172.16.0.14_prescript.pp
Error: Could not start Service[iptables]: Execution of '/sbin/service iptables start' returned 6:

This happens when the file /etc/sysconfig/iptables does not exist. Creating an empty file at /etc/sysconfig/iptables allows the service script to run without error.

Attila Fazekas (afazekas) wrote :

It also happens with RHEL6.x.

Changed in packstack:
status: New → Confirmed
Martin Mágr (mmagr) wrote :

This should be fixed with most recent version of Puppet modules package: openstack-puppet-modules-2014.1-7.el6.

Attila Fazekas (afazekas) wrote :

EL6 does not uses systemd, the systemd systems had a different iptables issue (service package was not installed).

The issue happens also with:
openstack-packstack-puppet-2014.1.1-0.10.dev1065
openstack-packstack-2014.1.1-0.10.dev1065

'Creating an empty file at /etc/sysconfig/iptables allows the service script to run without error.'

Lars Kellogg-Stedman (larsks) wrote :

I have submitted a change to the puppetlabs firewall module:

https://github.com/puppetlabs/puppetlabs-firewall/pull/365

Mingyu Li (mingyu-li-cn) wrote :

Is this bug fixed or not? I was affected by a similar bug when running packstack on CentOS 7.

Attila Fazekas (afazekas) wrote :

The issue was fixed long time ago, just this bug status was not updated.
If you see similar issue, you should open a new bug.

Changed in packstack:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers