Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1380732 - Unable to resolve templates under OS tab when selecting compute resource as Azure
Summary: Unable to resolve templates under OS tab when selecting compute resource as A...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - Azure
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: Daniel Lobato Garcia
QA Contact: Kedar Bidarkar
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-30 12:39 UTC by Kedar Bidarkar
Modified: 2019-08-12 16:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-05 17:06:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Templates not resolved (55.91 KB, image/png)
2016-09-30 12:42 UTC, Kedar Bidarkar
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 16758 0 None None None 2016-09-30 15:01:35 UTC

Description Kedar Bidarkar 2016-09-30 12:39:21 UTC
Description of problem:

When using Compute Resource as Azure, we are unable to resolve templates under OS tab.



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


How reproducible:


Steps to Reproduce:
1. Add Azure compute resource 
2. While creating a "New Host" under the Operating System tab , populate all the values and then click the "Resolve" button.
3. 

Actual results:
Upon clicking the "Resolve" button "Sorry but no templates were configured." 

Expected results:
Upon clicking the "Resolve" button, it should resolve all the templates.

Additional info:

Comment 1 Kedar Bidarkar 2016-09-30 12:42:30 UTC
Created attachment 1206253 [details]
Templates not resolved

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

Comment 4 Bryan Kearney 2016-10-03 16:20:28 UTC
Upstream bug assigned to dlobatog

Comment 5 Bryan Kearney 2016-10-03 16:20:31 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16758 has been resolved.

Comment 9 Satellite Program 2017-10-02 14:10:51 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16758 has been resolved.

Comment 13 Bryan Kearney 2018-07-05 17:06:34 UTC
Closing this out as next release.

Comment 14 Bryan Kearney 2018-07-05 17:47:29 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.


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