Bug 1372028 - Provisioning : Azure stack provisioning request fails
Summary: Provisioning : Azure stack provisioning request fails
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Provisioning
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.7.0
Assignee: Bill Wei
QA Contact: Dave Johnson
URL:
Whiteboard: service
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-31 18:07 UTC by Shveta
Modified: 2016-09-13 04:57 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-06 22:14:13 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:

Attachments (Terms of Use)
automation log (787.50 KB, application/zip)
2016-08-31 18:07 UTC, Shveta 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Shveta 2016-08-31 18:07:31 UTC 
Created attachment 1196484 [details]
automation log

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Error - " [] {"message":"No HTTP resource was found that matches the request URI 'https://management.azure.com/subscriptions/9ee63d8e-aee7-4121-861c-d67a5b8d231e/resourcegroups/?api-version=2016-06-01'."} (MiqException::MiqOrchestrationProvisionError) "
2.
3.

Actual results:


Expected results:


Additional info:
Build : 5.6.1.2.20160810181333_8ba817b
Comment 3 Bill Wei 2016-09-01 14:21:20 UTC 
The problem occurred at creating new resource group. It seems at the ordering time you wanted to create a new resource group but did not give a valid resource group name. Here is the dialog options:

options: {:dialog=>{"dialog_tenant_name"=>nil, "dialog_stack_name"=>"testI25Zq1CBzX", "dialog_resource_group"=>nil, "dialog_new_resource_group"=>"", "dialog_deploy_mode"=>"Incremental", ... }
Comment 4 Shveta 2016-09-06 22:14:13 UTC 
Checked with other Azure account .
Works fine .
Note You need to log in before you can comment on or make changes to this bug.