Ansible Linklight Failure New Insight Setup

jgholt commented 5 years ago

SUMMARY

Trying to Launch Linklight demo from Tower. Getting fatal error fatal: [jholt-linklight-test1-student1-host1]: FAILED! => { "msg": "Timeout (12s) waiting for privilege escalation prompt: " }

ISSUE TYPE

Bug Report

COMPONENT NAME

<34.234.234.204> SSH: EXEC ssh -C -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o Port=22 -o 'IdentityFile="/var/lib/awx/projects/_8__linklight/provisioner/jholt-linklight-test1/jholt-linklight-test1-private.pem"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=ec2-user -o ConnectTimeout=10 -o ControlPath=/tmp/awx_32_t0MSfs/cp/0af7a7e65d -tt 34.234.234.204 '/bin/sh -c '"'"'sudo -H -S -n -u root /bin/sh -c '"'"'"'"'"'"'"'"'echo BECOME-SUCCESS-rcqzltllrwpqnaztumknohmnhiypvloq; /usr/bin/python /home/ec2-user/.ansible/tmp/ansible-tmp-1549464221.05-260207850111909/AnsiballZ_group.py'"'"'"'"'"'"'"'"' && sleep 0'"'"''
fatal: [jholt-linklight-test1-student1-ansible]: FAILED! => {
"msg": "Timeout (12s) waiting for privilege escalation prompt: "

fatal: [jholt-linklight-test1-student1-host1]: FAILED! => {
"msg": "Timeout (12s) waiting for privilege escalation prompt: "

ANSIBLE VERSION

ansible 2.7.5

CONFIGURATION

OS / ENVIRONMENT

Running Tower Tower 3.4.0 on RHV.
RHV > Tower > AWS for linklight provisioning.

DEPENDENCY PROBLEMS

STEPS TO REPRODUCE

Brand New Tower Setup Brand New AWS Account Running the provisioner/provision_lab.yml in my Originial playbook ran for ~1 hour and then fails with above output.

provisioner/provision_lab.yml

https://gist.github.com/jgholt/f9883a9bd1388dd2d59c57282f7d5d23.js

EXPECTED RESULTS

The AWS portion seems to provision correctly, however, not sure where in the process it fails

ACTUAL RESULTS

https://gist.github.com/jgholt/f9883a9bd1388dd2d59c57282f7d5d23.js

IPvSean commented 5 years ago

looks like it could be related to: https://github.com/ansible/ansible/issues/33699

doing some more research

IPvSean commented 5 years ago

can you change to this branch https://github.com/network-automation/linklight/tree/feb6-2019 and retest for me?

jgholt commented 5 years ago

Got a little further.. But still had failure. Attaching log job_41.txt

IPvSean commented 5 years ago

TASK [aws_workshop_login_page : DNS FOR STUDENT WEBPAGE FOR US-EAST-1] *********
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Zone rhdemo.io. does not exist in Route53"}

@jgholt this just means you don't have DNS setup. This is not something I can automate, as you do not have access to my rhdemo.io DNS domain. You need to add a variable workshop_dns_zone and make it a DNS name in AWS route53. Just make a route53 entry (e.g. jgholt.io) and change that variable and you should be golden.

Can you retest? I am going to merge PR once we confirm this is working for you.

jgholt commented 5 years ago

failed again. Logs attached.
TASK [control_node : Put student inventory in proper spot (NETWORKING MODE)] *** fatal: [test1-student1-ansible]: FAILED! => {"msg": "Timeout (12s) waiting for privilege escalation prompt: "}

job_57.txt

jgholt commented 5 years ago

Tried again from a dedicated machine, not a VM running on a hypervisor and this ran successfully. I am guessing this could be a disk, or networking latency issue.

ansible / workshops