1726386 – Disabling host notifications also removes the host from Ansible inventory management.

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.

Bug 1726386 - Disabling host notifications also removes the host from Ansible inventory management.

Summary: Disabling host notifications also removes the host from Ansible inventory man...

Keywords:
Status:	CLOSED WONTFIX
Alias:	None
Product:	Red Hat Satellite
Classification:	Red Hat
Component:	Ansible - Configuration Management
Sub Component:
Version:	6.5.0
Hardware:	Unspecified
OS:	Unspecified
Priority:	high
Severity:	medium
Target Milestone:	Unspecified
Assignee:	satellite6-bugs
QA Contact:	Lukas Pramuk
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2019-07-02 17:59 UTC by Paul Dudley
Modified:	2024-06-13 22:09 UTC (History)
CC List:	2 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2022-09-02 15:17:51 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Bugzilla	1607550	0	high	CLOSED	Ansible Tower inventory integration is slow	2023-10-06 17:51:21 UTC

Description Paul Dudley 2019-07-02 17:59:00 UTC

Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Paul Dudley 2019-07-02 18:03:20 UTC

Set Component after typing and it looks like that wiped the initial description. Apologies. The real description is:

Description of problem:

Using Satellite 6 as inventory source for Ansible Tower. If a host has notifications disabled in Satellite, the host is disabled in the resultant inventory.

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

How reproducible:

Configure the Satellite 6 as inventory source for Ansible Tower, and disable the notification for a host.

Steps to Reproduce:

1. Configure the Satellite 6 as inventory source for Ansible Tower.
2. Synchronize the source inventory on the Ansible Tower.
3. Select a host on the Satellite and disable the notifications via WebUI
4. Synchronize the source inventory on the Ansible Tower.
5. The host that was notification disabled was turned off on the inventory.


Additional Information:
It looks like changing the notification flag not only changes configuration_status_label but also sets the enabled value as well. Are both of these changes intended? If so, is it intended to turn off Ansible Tower management of a host via this method?

~~~
]# diff /tmp/disabled /tmp/enabled
9c9
<   updated_at: '2019-06-04 13:28:07 UTC'
---
>   updated_at: '2019-06-04 13:30:27 UTC'
24c24
<   configuration_status_label: Alerts disabled
---
>   configuration_status_label: No changes
73c73
<   enabled: false
---
>   enabled: true
~~~

Comment 5 Marek Hulan 2019-07-16 15:55:46 UTC

I can confirm the behavior. The reason is, "enabled" is one of the top-level inventory attribute in Satellite. At the same time, it seems to have special meaning in tower. We can't easily change the inventory format in Satellite (backwards compatibility). This should be fixed by bigger effort of redesigning how we generate the inventory for tower. We shouldn't probably rely on puppet inventory and properly namespace custom foreman attributes. This is related to BZ 1607550. The fix will need to land in all of foreman, foreman_ansible, ansible projects.

Comment 7 Mike McCune 2022-01-28 22:33:49 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 8 Mike McCune 2022-07-08 17:15:31 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 9 Brad Buckingham 2022-09-02 20:08:50 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.