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 2153548 - [RFE] Satellite 6.12 is still using katello-ca to register hosts during provisioning instead of Global Registration Template
Summary: [RFE] Satellite 6.12 is still using katello-ca to register hosts during provi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning
Version: 6.12.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: 6.15.0
Assignee: nalfassi
QA Contact: sganar
Zuzana Lena Ansorgova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-14 18:18 UTC by Arzoo Singh
Modified: 2024-05-08 13:58 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
.Provisioning templates now use the Global Registration method to register hosts Previously, provisioning templates used the Katello CA Consumer to register hosts during provisioning, which is deprecated and not compatible with newer RHEL systems. With this release, provisioning templates register hosts by using the same method as the Global Registration template, because they include the shared `subscription_manager_setup` snippet.
Clone Of:
Environment:
Last Closed: 2024-04-23 17:12:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36747 0 Low New Satellite 6.12 is still using katello-ca to register hosts during provisioning instead of Gloabl Registration Template 2023-09-14 15:04:39 UTC
Red Hat Issue Tracker SAT-16970 0 None None None 2023-04-05 12:46:00 UTC
Red Hat Issue Tracker SAT-19529 0 None None None 2023-09-22 05:59:31 UTC
Red Hat Product Errata RHSA-2024:2010 0 None None None 2024-04-23 17:12:59 UTC

Comment 1 Leos Stejskal 2023-01-17 10:12:36 UTC 
Hi,
Global registration is for registering already running hosts outside of Satellite,
hosts that are provisioned from the Satellite are already in Satellite.

Maybe you meant subscribing host to the Satellite, is that what you want to do?
Comment 2 Jayant Bhatia 2023-01-23 14:21:47 UTC 
Hello,
The provisioning via Satellite is working absolutely fine for the user. But user is looking forward to use "Global registration template" while provisioning instead of existing workflow. This Bug has been filed to incorporate "Global registration template" to register/subscribe the hosts provisioned via Satellite instead of existing workflow since the manual steps to install katello-ca-consumer package and then running "subscription-manager register" command has been deprecated.
Comment 3 Leos Stejskal 2023-01-31 09:32:13 UTC 
This is going to be fixed in 6.13 where we don't use katello-ca rpm anymore,
see the template: https://github.com/theforeman/foreman/blob/3.5-stable/app/views/unattended/provisioning_templates/registration/global_registration.erb#L173-L177
Comment 4 Brad Buckingham 2023-04-05 12:44:43 UTC 
Based upon comment 3, adding to 6.14 and moving to POST for QE verification.
Comment 5 Leos Stejskal 2023-05-30 12:34:15 UTC 
Hi,
sorry for the hasty updates, this has not been fixed yet, for provisioning the issue is still there.
Moving to the NEW state.
Comment 7 nalfassi 2023-09-14 15:04:38 UTC 
Created redmine issue https://projects.theforeman.org/issues/36747 from this bug
Comment 8 Brad Buckingham 2023-10-30 11:29:29 UTC 
Bulk setting Target Milestone = 6.15.0 where sat-6.15.0+ is set.
Comment 10 Bryan Kearney 2023-11-30 20:02:13 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36747 has been resolved.
Comment 11 sganar 2023-12-12 16:32:34 UTC 
Verified.

Tested on Satellite 6.15.0 Snap 2.0


Steps followed: 
1. Configure a Satellite for provisioning
2. Provision a host(Make sure to use an activation key to register the host to the Satellite)
3. Observe the host while provisioning or Check `install.post.log` on the host after provisioning.

Observation: 
katello-ca-consumer is no longer been used in host registration, the host is registered using subscription-manager
Comment 17 errata-xmlrpc 2024-04-23 17:12:57 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
Note You need to log in before you can comment on or make changes to this bug.