CI: undercloud fails because iptables service fails to start

Bug #1686351 reported by Sagi (Sergey) Shnaidman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Critical
Unassigned

Bug Description

Seems like all TripleO CI jobs are affected:

http://logs.openstack.org/87/459787/1/check-tripleo/gate-tripleo-ci-centos-7-ovb-ha/ba7e54b/logs/undercloud/var/log/undercloud_install.txt.gz#_2017-04-26_08_42_42_000

Error: Systemd start for iptables failed!
 journalctl log for iptables:
-- Logs begin at Wed 2017-04-26 07:46:56 UTC, end at Wed 2017-04-26 08:42:42 UTC. --
Apr 26 08:42:42 tripleo-centos-7-tripleo-test-cloud-rh1-8594584 systemd[1]: Assertion failed for IPv4 firewall with iptables.
Error: /Stage[main]/Firewall::Linux::Redhat/Service[iptables]/ensure: change from stopped to running failed: Systemd start for iptables failed!
 journalctl log for iptables:
 -- Logs begin at Wed 2017-04-26 07:46:56 UTC, end at Wed 2017-04-26 08:42:42 UTC. --
 Apr 26 08:42:42 tripleo-centos-7-tripleo-test-cloud-rh1-8594584 systemd[1]: Assertion failed for IPv4 firewall with iptables.

Tags: ci
Changed in tripleo:
importance: Undecided → Critical
status: New → Triaged
milestone: none → ongoing
Revision history for this message
Paul Belanger (pabelanger) wrote :

This was caused by our unpuppet migration for nodepool images, it should be fixed now:

  https://review.openstack.org/#/c/458986/

Changed in tripleo:
status: Triaged → Fix Released
tags: removed: alert
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.