Description of problem: Installer failed at task `Configure AWS cloud provider` while enabling AWS cloudprovider for EC2 C5 instance. Go through of the issue, it appears that ansible is unable to get `ansible_virtualization_role` and `ansible_virtualization_type` for EC2 C5 instance: $ ansible -m setup all -i /tmp/c5_host |grep "virtualization" "ansible_virtualization_role": "NA", "ansible_virtualization_type": "NA", Checked on the EC2 C5 instance: # cat /sys/devices/virtual/dmi/id/bios_vendor Amazon EC2 # cat /sys/devices/virtual/dmi/id/sys_vendor Amazon EC2 # cat /sys/devices/virtual/dmi/id/product_name c5.large Checking on a normal EC2 instance: # cat /sys/devices/virtual/dmi/id/sys_vendor Xen # cat /sys/devices/virtual/dmi/id/product_name HVM domU # cat /sys/devices/virtual/dmi/id/bios_vendor Xen Version-Release number of the following components: ansible 2.4.2.0 openshift-ansible-3.9.0-0.16.0.git.0.9f19afc.el7.noarch How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Please include the entire output from the last TASK line through the end of output if an error is generated Expected results: Additional info: Please attach logs from ansible-playbook with the -vvv flag
Gan, can you provide more complete logs at -vvv level?
What version of boto is in use on this system?
# rpm -qa |grep boto python2-boto3-1.4.4-1.fc25.noarch python2-botocore-1.5.26-1.fc25.noarch python3-boto-2.45.0-3.fc25.noarch python2-boto-2.45.0-3.fc25.noarch # rpm -qa |grep ansible ansible-2.4.2.0-2.el7.noarch
Opened an Ansible issue: https://github.com/ansible/ansible/issues/35051
Proposed fix for openshift-anible: https://github.com/openshift/openshift-ansible/pull/6792
This bug is targeted for 3.9, while this bug is attached to a 3.5/3.6/3.7 errata, pls attach it to a correct errata.
Fixed in openshift-ansible-playbooks-3.9.0-0.23.0.git.0.d53d7ed.el7.noarch.rpm
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0489