Hide Forgot
Created attachment 1139808 [details] service dialog and stack.json Description of problem: When adding the Azure provider and creating an image in azure the deployment via azure-single-vm-from-user-image does not complete. It stays in a pending state and loops around update provision status. I didn't debug what exit status is expected but it seems its not getting it back what it should. The azure-single-vm-from-user-image stack also does not create a public ip nor a dns name. It would be nice if this could be added. So it would probably also be an automate bug as it goes through orchestration. I can successfully create a vm with public ip with this azure-single-vm-from-user-image-pub-ip.json and azure-single-vm-from-user-image-pub-ip.yaml But the stack and automate run still get stuck in pending state. Version-Release number of selected component (if applicable): 5.5.2.4.20160127105142_395c086 How reproducible: Always Steps to Reproduce: 1. Create an azure provider and add an image 2. Use the azure-single-vm-from-user-image or my azure-single-vm-from-user-image-pub-ip and create a catalog item from it. 3. Provision a vm via orchestration to azure. Actual results: Automate run does not complete. With the azure-single-vm-from-user-image there is no public ip added nor a dns name. Expected results: Automate run should finish and public ip as well as dns name should be created. Additional info: See fixes for service dialog as well as azure-single-vm-from-user-image-pub-ip.json
GregM, this sounds like Automate/Orchestration.... Maybe Bill can take a look?
I confirmed the "Status Pending" issue on 5.5.3 and I don't believe it is a blocker. The IP Address and DNS should be separated as an RFE as it's not broken in the sense that it should be there. The template specifically states there will not be a Public IP address.
Clearing stale flag.
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.
I would recommend closing the BZ if no more problem is observed.
Recommendation agreed. For whatever reason, it's disappeared as mysteriously as it appeared. I've tested it with 5.5.3.3 and 5.5.3.4 and it works fine. To be clear, it was a bug. Too many of us saw it. Thanks to Laurant for all his time. An RFE should be opened for the Public IP if that is still wanted.