Comment 11 for bug 1773979

Revision history for this message
Sunil Basker (sunilbasker) wrote : Ansible error in VM

Guys,

When ‘configure_instances’ playbook fails when run on the VM, to install k8. Any idea on how to fix it?

TASK [configure_instances : restart network service] ***************************************************************************************************************************
fatal: [1.1.1.3]: FAILED! => {"changed": false, "msg": "Unable to start service network: Job for network.service failed because the control process exited with error code. See \"systemctl status network.service\" and \"journalctl -xe\" for details.\n"}
fatal: [1.1.1.5]: FAILED! => {"changed": false, "msg": "Unable to start service network: Job for network.service failed because the control process exited with error code. See \"systemctl status network.service\" and \"journalctl -xe\" for details.\n"}
fatal: [1.1.1.4]: FAILED! => {"changed": false, "msg": "Unable to start service network: Job for network.service failed because the control process exited with error code. See \"systemctl status network.service\" and \"journalctl -xe\" for details.\n"}
        to retry, use: --limit @/root/contrail-ansible-deployer/playbooks/configure_instances.retry

on rerun however, the playbook works and the same task in skipped

TASK [configure_instances : restart network service] ***************************************************************************************************************************
skipping: [1.1.1.3]
skipping: [1.1.1.5]
skipping: [1.1.1.4]

Sunil