Description of problem: Actions::Fusor::Deployment::Rhev::Deploy task fails just after both hypervisors are installed and restarted. The task fails with: 'Connection timed out - connect(2) for "hypervisor2.example.com" port 22' After resuming the task, it seems to be running. Last log entry from ansible: 'p=28066 u=foreman | TASK [self_hosted_first_host : Install dependences (~2GB)] ********************* p=28066 u=foreman | task path: /usr/share/ansible-ovirt/roles/self_hosted_first_host/tasks/main.yml:3' The task now runs for about ~2 hours without timeout and without noticeable change. Version-Release number of selected component (if applicable): QCI-1.1-RHEL-7-20161025.t.0 How reproducible: Happened to me once Steps to Reproduce: 1. Start a deployment of RHV self-hosted with 2 hypervisors (baremetal) 2. After both hypervisors are installed and restarted, the task fails 3. Actual results: Deployment failed; RHV Deploy task failed with connection timed out Expected results: Deployment successful Additional info:
Reproduced in a second deployment.
Can you give me the /var/log/messages of the two hosts, the /var/log/ovirt-hosted-engine-setup/* of the two hosts if it exists, and the /var/log/foreman/deployments/<deployment name>/ansible.log from the Satellite?
There is a good chance this is a duplicate of this BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1386398
I'm pretty sure this is a duplicate of the aforementioned BZ, so I'm going to go ahead and close this. *** This bug has been marked as a duplicate of bug 1386398 ***
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days