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.

I ran into the same issue when I was writing my python installation script for Foreman a few months back (https://github.com/hamiheim/foreman_installer). I'd recommend either updating the satellite module to use "dnf module switch-to" for both ruby and psql, or adding a step in the installer prior to installing the satellite module to run the switch-to module command for both modules. This will prevent errors about conflicting modules, and make the installation cleaner.

Reported by: bman12092

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html/installing_satellite_server_in_a_disconnected_network_environment/installing_server_disconnected_satellite#annotations:9b5c9d34-cf55-4c07-b161-ee22554276a9

Hello, 
Many thanks for using the Direct documentation Feedback tool to report this suggestion for improvement.
The Bugzilla will go through proper team triage, and the documentation team will inform about updates on the implmentation to product docs in this ticket.
Thank you!

The easier workaround is to just do all enablements in one go explicitly:

# dnf module enable ruby:2.7 postgresql:12 satellite:el8

But we deliberately only list the satellite module to not have to maintain a list of dependencies in multiple places (installer, docs, module metadata).

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days