Insufficient timeout when deploying openstack blueprint

[spisarski]

When configuring the OpenStack blueprint, the image found at http://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud.qcow2, rarely ever becomes active in the time allotted (5x30 seconds I believe) on our OpenStack pod which causes the blueprint to fail. I tried searching through all of the files to see if there were any options I could hack to no avail. Please see the output attached and let me know if you would need to see our openstack-manager-blueprint-inputs.yaml file.

os-man-bp.txt

Additionally, when this failure occurs, the 'cfy' executable returns 0, which is terrible when attempting to apply this blueprint via Ansible as I had been assuming all was well just to find out that it stopped trying.

[rahil2508]

Hi, Did anyone get a chance to look into this? Thanks.