Bug 2224467

Summary:	[RFE] The "Run Puppet Once" within "Schedule a job" dropdown on "Content Hosts" page in Satellite WebUI should be removed
Product:	Red Hat Satellite	Reporter:	Jayant Bhatia <jbhatia>
Component:	Remote Execution	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED NOTABUG	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	low	Docs Contact:
Priority:	low
Version:	6.14.0	CC:	aruzicka, rlavi
Target Milestone:	Unspecified	Keywords:	FutureFeature
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:	2023-08-02 12:53:25 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 Jayant Bhatia 2023-07-21 03:01:42 UTC

Description of problem:

Puppet is by default disabled in Satellite/Capsule 6.14 and it needs to be explicitly enabled if a user wish to use it. Since the Puppet will not be supported in the long run and is being planned to be deprecated, the "Run Puppet Once" within "Schedule a job" dropdown on "Content Hosts" page in Satellite WebUI should be removed


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


Steps to Reproduce:
1. Navigate to Satellite WebUI -> Hosts -> Content Hosts -> Click on the name of registered client host.
2. At the top right corner, click on "Schedule a job" drop down.


Actual results: The "Run Puppet Once" is listed as first option in the dropdown.


Expected results: The "Run Puppet Once" should be removed or should be pushed downwards as the last option. 


Additional info: Even if the "Run Puppet Once" option is removed, users can always execute puppet via remote execution jobs if needed.

Comment 2 Marek Hulan 2023-08-02 12:53:25 UTC

The Run puppet once functionality is not related to the puppet plugin presence. It is one of the REX action users can easily trigger on the host. There are customers using external puppet on their hosts. This job still works with such puppet agents. If the agent is not installed on the host, the result would be something like "command not found". The fact the puppet plugin was made optional does not mean every mention of puppet needs to be hidden if the plugin is not allowed. There are still many references in settings for the puppet functionality that remained part of the core (e.g. facts parsing).

Therefore we decided on the triage meeting to reject this RFE, please let me know if the rationale isn't clear.