Bug 2002505
| Summary: | Unable set deploy on "bare metal" in the child hostgroup if its parent hostgroup is set to use a compute resource | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Hao Chang Yu <hyu> |
| Component: | Host Group | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED MIGRATED | QA Contact: | Satellite QE Team <sat-qe-bz-list> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.9.0 | CC: | aruzicka, inecas, jalviso, kgaikwad, mark.barry, satellite6-bugs, smeyer |
| Target Milestone: | Unspecified | Keywords: | MigratedToJIRA, Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-06-06 01:03:36 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Hao Chang Yu
2021-09-09 03:20:22 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. (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? 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. 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. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |