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 2136901 - [RFE] Satellite clients should register during the installation and use the repositories
Summary: [RFE] Satellite clients should register during the installation and use the r...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning
Version: 6.12.0
Hardware: All
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-21 19:32 UTC by jcastran
Modified: 2024-06-06 12:47 UTC (History)
4 users (show)

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

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1940288 1 None None None 2023-09-09 07:43:25 UTC
Red Hat Bugzilla 2105441 0 high CLOSED RHEL 9 provisioned host goes into emergency mode after initial reboot 2024-11-12 07:54:55 UTC
Red Hat Issue Tracker   SAT-20448 0 None Migrated None 2024-06-06 12:47:15 UTC

Description jcastran 2022-10-21 19:32:08 UTC 
Currently Satellite clients install from a kickstart repository, then in a %post script, installs katello, registers to satellite, and then performs a "yum update"

With 8.3 and later, we are able to register during installation with the "rhsm" kickstart syntax.

The Request is that the %post script registration + update template should be replaced by this feature. If we register directly to the satellite this would bypass the need for a kickstart repository as well as make the installation one transaction, instead of 2 (install then update).


There are 2 bugs regarding this %post update process for RHEL 9 that this would also fix since there would be no need to update anyways.

https://bugzilla.redhat.com/show_bug.cgi?id=1940288
https://bugzilla.redhat.com/show_bug.cgi?id=2105441
Comment 1 Marek Hulan 2023-12-22 14:10:40 UTC 
I believe this has been resolved already but only for RHEL 9, not sure why this wasn't allowed for older RHEL versions. It should be easy to allows this for RHEL 8.3+ I believe.
Comment 2 Eric Helms 2024-06-06 12:47:17 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.
Note You need to log in before you can comment on or make changes to this bug.