On a meeting with afedorov@redhat.com, rhn-engineering-lstejska, rh-ee-nalfassi, rhn-engineering-mhulan we've decided to decouple the Satellite registration and the conversion - we'll require customers to register to Satellite prior to executing convert2rhel.

The main trigger for this change is that the katello package is going away with Satellite 6.16. Until then the https://<satellite.example.com>/pub/katello-ca-consumer-latest.noarch.rpm will still be available for download - which is what we tell customers now to use with convert2rhel if they want to use Satellite to access RHEL repos.

This change will have several benefits:

• customers will be able to use existing Satellite registration automation like Ansible roles
• customers will have the choice to pick the best option for registering their system with Satellite - there's quite a few
• in convert2rhel we wouldn't need to implement the registration and make it secure - it would just increase the complexity of the tool and make debugging of problems with the registration more difficult

Acceptance criteria:

• In convert2rhel all code related to the katello-ca-consumer package and Satellite is removed
  • For convert2rhel it does not matter whether the system is registered to Satellite or standard Red Hat CDN - all it needs is an access to RHEL repos through subscription-manager
• Documentation is updated to capture the following aspects of this change:
  • The customer will need to make sure that they register with an activation key that provides access to RHEL repositories.
  • If the system does not have access to the internet, the activation key will need to provide also the original vendor repos (e.g. CentOS, Oracle) because during the conversion convert2rhel needs access to them to be able to download certain original vendor packages for backup purposes.

Related:

• The Satellite folks will remove the katello package download from the Satellite convert to RHEL job template (https://bugzilla.redhat.com/show_bug.cgi?id=2253464)