Description of problem: Include Ansible modules for Satellite management with the Ansible Core modules. Disconnected environments can't download and use modules downloaded from 'random' locations on the internet. Adding satellite modules to the core Ansible modules will allow disconnected environments to use Ansible to install, configure, and manage their multiple Satellite installations. Version-Release number of selected component (if applicable): N/A - All How reproducible: Always. Many disconnected environments are using hammer commands to manage their environments, but this should be replaced with more streamlined and idempotent ansible modules. Examples: https://github.com/SatelliteQE/nailgun
Thanks for the report. How do you envision consuming these modules? Or do you want just that modules are shipped as part od Satellite in its repositories? Meaning this is packaging and supporting these ansible modules?
Marek, In many (I work in a few) disconnected environments, downloading additional content (not directly from Red Hat) is a monumental task. Having the ansible modules for Satellite included in the core Ansible modules (which get distributed with Ansible) or even with the Satellite content would be beneficial. Again this use case is in a disconnected environment. Content distributed by Red Hat as part of our product, is easier to justify bringing through to a disconnected network then something downloaded from another source. We are also finding that inside disconnected environments, we don't just have one Satellite server and capsule, but a large number of Satellite servers inside every network / disconnected customer. The number of disconnected Satellite installations is increasing every day, and having a standard (easy!) method for installing, managing, and configuring these installations is something that would greatly assist those of us managing them. Not asking to change the core installation from puppet to Ansible, but fast tracking the Satellite specific modules to be included with the core Ansible modules (if possible) would allow our consultants onsite in these disconnected environments to work more efficiently.
Isn't this a dupe of https://bugzilla.redhat.com/show_bug.cgi?id=1643188?
*** Bug 1643188 has been marked as a duplicate of this bug. ***
Ansible Collections are the content strategy of the future for Ansible. It appears that the existing Foreman/Satellite content has already been refactored into a collection which currently is available on Galaxy (https://galaxy.ansible.com/theforeman/foreman) and could be distributed via Automation Hub with BU support for customers who would like to download directly from Red Hat.
Created redmine issue https://projects.theforeman.org/issues/29234 from this bug
Verified on Satellite 6.8 snap 6, ansible-collection-redhat-satellite rpm provides the modules as expected
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.8 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-2020:4366