This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2002505 - Unable set deploy on "bare metal" in the child hostgroup if its parent hostgroup is set to use a compute resource
Summary: Unable set deploy on "bare metal" in the child hostgroup if its parent hostgr...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Host Group
Version: 6.9.0
Hardware: Unspecified
OS: Unspecified
high
high with 4 votes
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-09 03:20 UTC by Hao Chang Yu
Modified: 2024-10-05 04:25 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 01:03:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-20579 0 None Migrated None 2024-06-06 01:03:34 UTC

Description Hao Chang Yu 2021-09-09 03:20:22 UTC 
Description of problem:
There is no bare metal option to select in the "Deploy On" field when creating or updating a child host group and its parent host group is set to use a compute resource.

Steps to Reproduce:
1. Create a top most parent host group and set the "Deploy On" to any compute resource.
2. Create a child host group which inherit the above parent host group.

Actual results:
Missing "Bare Metal" or blank option in the "Deploy On" select box

Expected results:
Able to select Bare Metal

Additional info:

I think is the cause of the issue:

Unset/Blank value serves different purpose in the uppermost parent host group and child host group.

- For parent host group unset/blank value means set "Bare Metal" as the compute resource.
- For child host group unset/blank value means inherit the value from parent host group.

Due to this conflict, we are unable to set "Bare Metal" in the child host group.
Comment 5 Brad Buckingham 2023-10-04 21:43:14 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.
Comment 6 mark.barry 2023-10-04 22:24:37 UTC 
(In reply to Brad Buckingham from comment #5)
> Upon review of our valid but aging backlog the Satellite Team has concluded
> that this Bugzilla does not meet the criteria for a resolution in the near
> term, and are planning to close in a month. This message may be a repeat of
> a previous update and the bug is again being considered to be closed. If you
> have any concerns about this, please contact your Red Hat Account team. 
> Thank you.

I actually raised this defect via Red Hat support back on the 6th of July, 2020.  Refer to https://access.redhat.com/support/cases/#/case/02695292.  According to the updates on the ticket, there are two similar defects, which one has been marked by @bbuckingham as "Keywords: EasyFix, Patch, Triaged" back in September, 2021, refer to https://bugzilla.redhat.com/show_bug.cgi?id=2002533.  I appreciate that resolving defects take time and effort, however it has been over three years since the defect was raised and it appears that the issue is trivial to resolve.  If this is not the case, can a work around be provided via foreman-rake or similar utility?
Comment 9 Brad Buckingham 2023-11-02 16:58:11 UTC 
Based upon feedback during auto-closure, leaving this bugzilla open a while longer for additional investigation; however, it may be closed in a future iteration.
Comment 10 Eric Helms 2024-06-06 01:03:36 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Comment 11 Red Hat Bugzilla 2024-10-05 04:25:10 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.