Bug 1602873

Summary:	Ansible job templates in 6.4 aren't in the same categories as SSH templates
Product:	Red Hat Satellite	Reporter:	Stephen Benjamin <stbenjam>
Component:	Remote Execution	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Peter Ondrejka <pondrejk>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	aruzicka, inecas, mhulan
Target Milestone:	Unspecified	Keywords:	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:	2019-09-03 18:58:27 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 Stephen Benjamin 2018-07-18 17:04:02 UTC

Description of problem:

The job templates for Ansible have different categories than SSH.  It doesn't make sense to me why "Run Command - Ansible Default" is in an "Ansible Commands" job category, or the package action is in a category named Ansible Packages.

There are already "Command" and "Package" categories. It makes the categories list very long and results in poor usability for the end user.

Another way to think about it:  What's the point of categories if there's only one job template in each one?

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

How reproducible:
Always

Steps to Reproduce:
1. Schedule a remote job on a host, and look at the categories drop down

Actual results:
Ansible job templates have Ansible categories

Expected results:
Jobs are categorized generically


Additional info:

Comment 2 Marek Hulan 2018-07-20 07:35:58 UTC

This is required because otherwise the REX form renders fields for each provider. This is a bigger refactoring in REX to drop multiprovider support of single job invocation, which is why we decided to keep it separate. Also I'd first like to consult that with Rox, I think it might be more confusing to sometimes have category prefixed with Ansible (e.g. ansible play roles) and sometimes not and need to carefully select the job by name. Moving to REX as that's the plugin where majority needs to happen.

Comment 5 Stephen Benjamin 2018-07-20 12:04:23 UTC

> This is required because otherwise the REX form renders fields for each provider

Ah thanks, I didn't realize category was actually implemented that way, I thought it was only an administrative grouping of templates.

Comment 6 Bryan Kearney 2019-08-05 12:22:31 UTC

The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.

Comment 7 Bryan Kearney 2019-09-03 18:58:27 UTC

Thank you for your interest in Satellite 6. 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, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.