Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 2253464

Summary: [RFE] The 'Convert to RHEL' job template should use an alternative of katello-ca-consumer-latest.noarch.rpm
Product: Red Hat Satellite Reporter: Sayan Das <saydas>
Component: Conversions applianceAssignee: nalfassi
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.15.0CC: addubey, ahumbe, dsinglet, jlenz, lstejska, myee, nalfassi, rlavi
Target Milestone: UnspecifiedKeywords: FutureFeature, MigratedToJIRA, Triaged
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 16:37:57 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 Sayan Das 2023-12-07 14:52:56 UTC
Description of problem:

Right now, We have this job template in satellite, that makes use of katello-ca-consumer-latest.noarch.rpm

# hammer job-template dump --name "Convert to RHEL"
---
- hosts: all
<%- if input('Data telemetry') != "yes" -%>
  environment:
    CONVERT2RHEL_DISABLE_TELEMETRY: 1
<%- end -%>
  tasks:
    - name: Install convert2rhel
      ansible.builtin.package:
        name: convert2rhel
        state: present
    - name: Prepopulate katello-ca-consumer
      get_url:
        url: <%= subscription_manager_configuration_url(@host) %>
        dest: /usr/share/convert2rhel/subscription-manager/katello-ca-consumer-latest.noarch.rpm
    - name: Start convert2rhel
      command: convert2rhel -y --activationkey "<%= input_resource('Activation Key').name %>" --org "<%= @host.organization.label %>" --keep-rhsm
<%- if input('Restart') == "yes" -%>
    - name: Reboot the machine
      reboot:
        reboot_timeout: 1800
<%- end -%>
<%- # This will update system facts in Satellite and link the correct OS of the host %->
    - name: Update system facts
      command: subscription-manager facts --update


This is perhaps because the official documentation also documents the usage of this as a mandatory step for any Satellite\Capsule connected clients:

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/converting_from_an_rpm-based_linux_distribution_to_rhel/index#proc_preparing-for-a-rhel-conversion_converting-using-the-command-line

Step 9

######################
If you are accessing RHEL packages through a Red Hat Satellite server, download the consumer RPM to the /usr/share/convert2rhel/subscription-manager/ directory:

# curl --insecure --output /usr/share/convert2rhel/subscription-manager/katello-ca-consumer-latest.noarch.rpm https://<satellite.example.com>/pub/katello-ca-consumer-latest.noarch.rpm

Replace satellite.example.com with the hostname of your Satellite server.
######################

Assuming that we are moving away from katello-ca-consumer-latest.noarch.rpm, We should confirm if we really need katello-ca-consumer-latest.noarch.rpm for the c2r operation and 

If yes, then when ?
If no, then lets get rid of it from job templates as well as documentation 


Version-Release number of selected component (if applicable):

All Satellite 6 versions containing the job template "Convert to RHEL"


How reproducible:

100%


Steps to Reproduce:
1.
2.
3.

Actual results:

The converted system ends up with katello-ca-consumer installed and due to the hardcoded task in template, we still have this dependency left for katello-ca-consumer-latest.noarch.rpm


Expected results:

Either confirm that the rpm is no longer needed with c2r or else develop an alternate solution for it to use with c2r workflow 


Additional info:

NA

Comment 2 Leos Stejskal 2024-01-12 08:22:38 UTC
Summary of the discussion we had with the Convert2RHEL team:

This won't be needed anymore, as the Convert2RHEL tool will drop the depending
on the katello-ca-consumer.rpm, and users must do these steps manually (if needed).
So after that, we can drop it from the template as well.

Assigning to @Nofar

Comment 3 Eric Helms 2024-06-06 16:37:57 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.