Bug 1855241 - foreman_lifecycle_environment_<env> group is missing in Satellite's inventory group in Ansible Tower after upgrade to Satellite 6.7
Summary: foreman_lifecycle_environment_<env> group is missing in Satellite's inventory...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Ansible
Version: 6.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Lukas Pramuk
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-09 10:25 UTC by Satyajit Das
Modified: 2022-10-28 18:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-10-28 18:00:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github theforeman foreman-ansible-modules issues 919 0 None closed Foreman inventory does not sync empty groups 2020-11-11 17:21:49 UTC

Description Satyajit Das 2020-07-09 10:25:31 UTC
Description of problem:

foreman_lifecycle_environment_<env> group is missing in Satellite's inventory group in Ansible Tower after upgrade to Satellite 6.7


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

How reproducible:
100%


Steps to Reproduce:

1. Configuring Satellite as a Dynamic Inventory in Ansible Tower.
2. Post inventory sync the foreman_lifecycle_environment_<env> group is missing

Actual results:

foreman_lifecycle_environment_<env> group is not getting sync post satellite upgrade to 6.7. In Satellite 6.6 it is working.


Expected results:

foreman_lifecycle_environment_<env> group should be available post Satellite's dynamic inventory sync.

Additional info:
Refer to the article for the screenshots.
=====================================
https://www.redhat.com/en/blog/satellite-and-ansible-tower-integration-part-1-inventory-integration

Comment 1 Brad Buckingham 2022-09-02 20:25:18 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 2 Brad Buckingham 2022-09-02 20:31:26 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 3 Brad Buckingham 2022-10-28 18:00:09 UTC
Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.


Note You need to log in before you can comment on or make changes to this bug.