Error occurs when starting iptables in version 2014.2.dev1468.gd049ea9

Bug #1451228 reported by Mingyu Li
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Packstack
New
Undecided
Unassigned

Bug Description

This bug is found in version "packstack Juno 2014.2.dev1468.gd049ea9". The CentOS version was "3.10.0-123.el7.x86_64"

Packstack can not start iptables when it runs on a node with CentOS 7 and without iptables and iptable-services installed. The error message is:
"PuppetError: Error appeared during Puppet run: 192.168.93.157_prescript.pp
Error: Could not start Service[iptables]: Execution of '/usr/bin/systemctl start iptables' returned 6: Failed to issue method call: Unit iptables.service failed to load: No such file or directory."

After this error occurs, if you re-run packstack on the same node, this error will not occur again. In fact, after that error, you can successfully start iptables manually, as shown in the attachment. So iptables and iptable-services must be installed by packstack correctly but packstack fails to start them at a right time or in a right order.

How to reproduce:
1. Install CentOS 7 with minimal installation.
2. yum update
3. yum install https://rdoproject.org/repos/rdo-release.rpm
   (juno-1)
4. yum install openstack-packstack
5. packstack --allinone
   or
   packstack --install-hosts=...

In prescript.pp.log:
"Error: Could not start Service[iptables]: Execution of '/usr/bin/systemctl start iptables' returned 6: Failed to issue method call: Unit iptables.service failed to load: No such file or directory.
Wrapped exception:
Execution of '/usr/bin/systemctl start iptables' returned 6: Failed to issue method call: Unit iptables.service failed to load: No such file or directory.
Error: /Stage[main]/Firewall::Linux::Redhat/Service[iptables]/ensure: change from stopped to running failed: Could not start Service[iptables]: Execution of '/usr/bin/systemctl start iptables' returned 6: Failed to issue method call: Unit iptables.service failed to load: No such file or directory."

In openstack-setup.log:
"2015-05-03 09:34:51::ERROR::run_setup::1018::root:: Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/packstack/installer/run_setup.py", line 1013, in main
    _main(options, confFile, logFile)
  File "/usr/lib/python2.7/site-packages/packstack/installer/run_setup.py", line 655, in _main
    runSequences()
  File "/usr/lib/python2.7/site-packages/packstack/installer/run_setup.py", line 626, in runSequences
    controller.runAllSequences()
  File "/usr/lib/python2.7/site-packages/packstack/installer/setup_controller.py", line 81, in runAllSequences
    sequence.run(config=self.CONF, messages=self.MESSAGES)
  File "/usr/lib/python2.7/site-packages/packstack/installer/core/sequences.py", line 109, in run
    step.run(config=config, messages=messages)
  File "/usr/lib/python2.7/site-packages/packstack/installer/core/sequences.py", line 50, in run
    self.function(config, messages)
  File "/usr/lib/python2.7/site-packages/packstack/plugins/puppet_950.py", line 254, in apply_puppet_manifest
    wait_for_puppet(currently_running, messages)
  File "/usr/lib/python2.7/site-packages/packstack/plugins/puppet_950.py", line 126, in wait_for_puppet
    validate_logfile(log)
  File "/usr/lib/python2.7/site-packages/packstack/modules/puppet.py", line 107, in validate_logfile
    raise PuppetError(message)
PuppetError: Error appeared during Puppet run: 192.168.93.157_prescript.pp
Error: Could not start Service[iptables]: Execution of '/usr/bin/systemctl start iptables' returned 6: Failed to issue method call: Unit iptables.service failed to load: No such file or directory.
You will find full trace in log /var/tmp/packstack/20150503-092452-GOTW1p/manifests/192.168.93.157_prescript.pp.log"

Revision history for this message
Mingyu Li (mingyu-li-cn) wrote :
Mingyu Li (mingyu-li-cn)
summary: - Error occurs when starting iptables
+ Error occurs when starting iptables in version 2014.2.dev1468.gd049ea9
Mingyu Li (mingyu-li-cn)
description: updated
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.