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 2068263 - Specifying a Host Group breaks Discovery Image Provisioning
Summary: Specifying a Host Group breaks Discovery Image Provisioning
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Discovery Image
Version: 6.9.9
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: 6.15.0
Assignee: satellite6-bugs
QA Contact: addubey
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-24 18:54 UTC by Griffin Sullivan
Modified: 2024-05-03 14:37 UTC (History)
7 users (show)

Fixed In Version: foreman_discovery-23.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-04-23 17:11:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Hotfix RPM for Satellite 6.14.4 (15.94 MB, application/x-rpm)
2024-05-03 14:37 UTC, Ian Ballou
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github theforeman foreman_discovery pull 609 0 None open Fixes BZ#2238952 - Selecting host group change form URL 2023-11-13 13:52:59 UTC
Red Hat Issue Tracker SAT-18653 0 None None None 2023-06-27 11:32:14 UTC
Red Hat Product Errata RHSA-2024:2010 0 None None None 2024-04-23 17:11:05 UTC

Comment 4 Leos Stejskal 2023-10-05 09:41:35 UTC
Hi, the reported 6.9 version is quite out of date,
is this issue also reproducible on newer versions, for example on 6.13?

Comment 5 Sayan Das 2023-10-06 13:22:59 UTC
I had reported this issue in the other BZ https://bugzilla.redhat.com/show_bug.cgi?id=2069324#c4 and in Comment 7, I confirmed that the issue still existed on Sat 6.13.

Comment 6 Griffin Sullivan 2023-10-26 11:47:49 UTC
Leos,

Seems like Sayan has answered what you were requesting. For more testing questions, I would point them to the Rocket QE team, since I no longer have a setup for testing discovery anymore.

Comment 7 Brad Buckingham 2023-10-30 11:29:29 UTC
Bulk setting Target Milestone = 6.15.0 where sat-6.15.0+ is set.

Comment 12 errata-xmlrpc 2024-04-23 17:11:04 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.15.0 release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2024:2010

Comment 13 Ian Ballou 2024-05-03 14:37:21 UTC
Created attachment 2031136 [details]
Hotfix RPM for Satellite 6.14.4

A hotfix RPM is available for this BZ for Satellite 6.14.4

INSTALL INSTRUCTIONS:

1. Create a complete backup or snapshot of Satellite 6.14.4 server

2. Download the hotfix RPM from this attachment

3. # dnf install ./rubygem-foreman_discovery-22.0.4-2.HOTFIXRHBZ2238952_2068263.el8sat.noarch.rpm --disableplugin=foreman-protector

4. # satellite-maintain service restart


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