RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.

Description of problem:
The Microsoft SQL role doesn't appear to support customers utilizing custom/internal yum repositories to provide the RPM content.  The role should support configuring a role variable to specify alternate yum repository locations (for example provided by Satellite) and should be able to operate in a disconnected environment.  Customers also might wish to use Satellite repositories to provide content management via functionality like Satellite Content Views 


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


How reproducible:
Every time


Steps to Reproduce:
1. Attempt to use role in disconnected environment

I'm not familiar with Satellite. I'm not sure how I'm going to test this. Can someone point me to documentation?

@dyeisley You will need to find some QE Satellite and import the Microsoft repositories into it as custom content. You can find info about this here: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.9/html/content_management_guide/importing_custom_content
Then, run the role with mssql_rpm_key, mssql_server_repository, mssql_client_repository variables pointing to Satellite to get content from there.

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 (ansible-collection-microsoft-sql bug fix and enhancement update), 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/RHBA-2022:1971