Playbook for installing OCP stops everytime at the task - 'Start and enable iptables service'

[openshiftdemos]

Playbook for installing OCP stops everytime at the task - 'Start and enable iptables service'

[thoraxe]

Is this still a problem now that we have made the machines bigger?

[kmurudi]

can start installing after 2-3 minutes after ssh-ing into master host. will test again and let know by evening

[thoraxe]

Any updates? IDM issues are separate.

[dmesser]

I think the workaround Ryan introduced to pre-enable iptables.service and disable firewalld.service works. You just have to wait for cloud-init to finish and ensure that iptables.service is indeed active. Then you can start the install and it works.
With the previous cloud-init steps this (iptables active) could take 2-3 minutes to be done due to long-running bash scripts. Now with cloud-init executing ansible playbooks it was much faster for me (~40-60 secs after instance boot) last time I checked.
Eventually we can use a wait-condition to signal the user successful rollout of the lab from a CFN standpoint so that the wait-condition would only fire when the last step of cloud-init ran successfully. That would include iptables.service activation and the user only enters the lab environment when this is definitely done and can rollout out OpenShift immediately.