Bug 1380741 - unable to select azure location field while creating compute-profiles
Summary: unable to select azure location field while creating compute-profiles
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - Azure
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
high
high vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Kedar Bidarkar
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-30 12:52 UTC by Kedar Bidarkar
Modified: 2019-04-01 20:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-31 12:43:57 UTC
Target Upstream Version:


Attachments (Terms of Use)
Unable to select location while creating a compute profile (51.51 KB, image/png)
2016-09-30 12:52 UTC, Kedar Bidarkar
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 16759 0 None None None 2016-09-30 15:03:19 UTC

Description Kedar Bidarkar 2016-09-30 12:52:22 UTC
Created attachment 1206254 [details]
Unable to select location while creating a compute profile

Description of problem:

Unable to select azure location field while creating compute-profiles


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

How reproducible:


Steps to Reproduce:
1. Make sure an image is added under the Azure Compute-Resource
2. Create a compute profile via the Azure Compute-Resource 
3. Unable to select the Azure location

Actual results:
We get a message saying "Choose an operatingsystem and image first"


Expected results:

We should be able to select the location.

Additional info:

Comment 1 Daniel Lobato Garcia 2016-09-30 14:34:33 UTC
Created redmine issue http://projects.theforeman.org/issues/16759 from this bug

Comment 3 Bryan Kearney 2017-08-31 12:43:57 UTC
Closing this out until we deliver https://bugzilla.redhat.com/show_bug.cgi?id=1201146.


Note You need to log in before you can comment on or make changes to this bug.