Unit iptables.service could not be found.

[0xmichalis]

TASK [Check if iptables is running] ********************************************
task path: /usr/share/ansible/openshift-ansible/playbooks/common/openshift-cluster/upgrades/init.yml:72
fatal: [localhost]: FAILED! => {
    "changed": false, 
    "cmd": [
        "systemctl", 
        "status", 
        "iptables"
    ], 
    "delta": "0:00:00.005048", 
    "end": "2017-04-19 05:59:21.620269", 
    "failed": true, 
    "generated_timestamp": "2017-04-19 05:59:21.643407", 
    "rc": 4, 
    "start": "2017-04-19 05:59:21.615221", 
    "stderr": [
        "Unit iptables.service could not be found."
    ], 
    "stdout": [], 
    "warnings": []
}

https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_extended_conformance_install_update/215/consoleFull#-14246886155849c75fe4b0052e114d805c

[sdodson]

That's actually not a fatal error, the playbook failed elsewhere. Regardless we've fixed this on master, so backporting to openshift-ansible release-1.5.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale