Bug 1649749

Summary:	foreman-maintain runs preparation_steps of whitelisted steps
Product:	Red Hat Satellite	Reporter:	Ales Dujicek <adujicek>
Component:	Satellite Maintain	Assignee:	Anurag Patel <apatel>
Status:	CLOSED WONTFIX	QA Contact:	Nikhil Kathole <nkathole>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.5.0	CC:	apatel, inecas, kgaikwad, mbacovsk
Target Milestone:	Unspecified	Keywords:	Triaged
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:		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 Ales Dujicek 2018-11-14 12:42:47 UTC

Description of problem:

foreman-maintain runs preparation_steps of whitelisted steps

for example:
# foreman-maintain upgrade check -y --target-version 6.4 --whitelist=disk-performance
Running preparation steps required to run the next scenarios
================================================================================
Procedures::Packages::Install: 
Loaded plugins: product-id, search-disabled-repos, subscription-manager
...
--> Running transaction check
---> Package fio.x86_64 0:3.1-2.el7 will be installed
--> Finished Dependency Resolution
...
Installing:
 fio                            x86_64                            3.1-2.el7                               Sat6-
...

but installation of fio is defined as preparation step for whitelisted disk-performance:

https://github.com/theforeman/foreman_maintain/blob/f8cfc2178e3eb949917a0ae78e1a4132e809b8e3/definitions/checks/disk/performance.rb#L8

Version-Release number of selected component (if applicable):
rubygem-foreman_maintain-0.2.11-1.el7sat.noarch

How reproducible:
always

Comment 4 Bryan Kearney 2019-12-03 16:34:40 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 5 Bryan Kearney 2020-01-15 20:30:21 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.

Comment 6 Bryan Kearney 2020-01-15 20:30:23 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.