Hide Forgot
*** Bug 1322832 has been marked as a duplicate of this bug. ***
This is working again in 5.5.3.3 I'm pretty sure the hack to get 5.5.2 to work was a bad idea and maybe this puts it to bed. Ideas? Ok Finished 306,000,000,000,001 Administrator Service Provision 04/06/16 22:33:36 UTC Provisioning Service [ProvisionAzureVM] from [ProvisionAzureVM] Approved Administrator 04/06/16 22:25:05 UTC 04/06/16 22:24:51 UTC 04/06/16 22:33:36 UTC Auto-Approved Service Provisioned Successfully
1. Whether a public IP is generated is determined by the template. The sample one shipped with the product does not assign public IP. 2. I did three tests using the environment provided by ldomb with build 5.5.2.4.20160127105142_395c086. Two succeeded and one failed with reasonable reason. I do not observed the issue with hanging in pending state. Note the request can take quite sometime to complete. 3. I looked at some of the failed requests on the system, all finished (complete or failed). I looked particularly at stack 'marcotest'. Its status is failed. For Azure orchestration provisioning to get failure reason, we normally need to examine the resources of the stack. For this particular test, resources do not indicate any error, yet the stack status is failed. I double checked with the provider using Azure API, the stack status is still failed yet resources have no error. This proves the problem is not on CFME side. 4. I also notice all provisionings with failed status are deployed with Complete mode. This is not advised. Please always use Incremental mode. See https://bugzilla.redhat.com/show_bug.cgi?id=1322082 for more details.
Closing because the original report https://bugzilla.redhat.com/show_bug.cgi?id=1320776 is verified not a bug