Bug 1726386

Summary:	Disabling host notifications also removes the host from Ansible inventory management.
Product:	Red Hat Satellite	Reporter:	Paul Dudley <pdudley>
Component:	Ansible - Configuration Management	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Lukas Pramuk <lpramuk>
Severity:	medium	Docs Contact:
Priority:	high
Version:	6.5.0	CC:	cdonnell, mhulan
Target Milestone:	Unspecified	Keywords:	PrioBumpGSS, PrioBumpQA, Triaged, UserExperience
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-09-02 15:17:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.