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.

+++ This bug was initially created as a clone of Bug #2022648 +++

Description of problem:

Ohai,
this is mostly a tracker for the inclusion of the 3.0.0 version of our collection.

The actual code changes are in https://github.com/RedHatSatellite/satellite-ansible-collection/pull/37
This then needs packaging
And release notes as this is a release with breaking changes.

Breaking changes:
- Support for Ansible 2.8 was removed -- this shouldn't affect any Satellite customers, as their setups run with 2.9 anyways, but still good to call out.
- Inventory plugin now defaults to the Reports API (instead of Hosts API). Users who had use_reports_api=True in their configs already won't notice any changes. Others might notice slightly different output of the inventory. If needed, this can be reverted by using the use_reports_api=False configuration option.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

*** This bug has been marked as a duplicate of bug 2022648 ***