Bug 1673862

Summary:	[RFE] Enable search for machines by power state
Product:	Red Hat Satellite	Reporter:	Maxim Burgerhout <mburgerh>
Component:	Compute Resources	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Lukáš Hellebrandt <lhellebr>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	egolov, kgaikwad, mhulan, oprazak
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:	2020-04-02 12:34:24 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 Maxim Burgerhout 2019-02-08 10:21:47 UTC

Description of problem:
There is not option to search for machines that are powered on.

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

How reproducible:
Try and search for machines (VMs) that are powered on

Steps to Reproduce:
1. Go to hosts page
2. Click search bar
3.

Actual results:
You notice that are option exists to search for machines in a certain power state

Expected results:
A search option for machines in a certain power state exists (paused, powered on, powered off), for easy scheduling of Ansible jobs (for powered on machines), or power events (powering on machines that are off).


Additional info:
This would be extra useful when scheduling a recurring job on Sat6 to run Ansible roles at a set interval. You only want those to run on machines that are powered when the job is run.

Comment 3 Evgeni Golov 2019-02-08 10:34:10 UTC

While being able to filter hosts by power state would be a very nice addition, I fear it will be "too expensive".

The power state of a host is queried live from the BMC/VM infra, and if you'd do this on *all* hosts at once, you'd end up waiting for quite some time until all the hosts responded.

But that's for PM/DEV to decide :)

Comment 4 Marek Hulan 2019-02-11 14:13:38 UTC

I agree with Evgeni, this is hard to achieve without some kind of caching. Then the question arise, wouldn't the cache be a problem here? Having old power status info in DB could cause many false alerts.

Comment 5 Maxim Burgerhout 2019-02-11 14:39:08 UTC

Well, we don't want to put extra pressure on the system by making expensive queries to VM / BMC infra, and I agree caching the power state in the DB doesn't really help. Would having a live gofer connection be more easy to query? That indicates a running client system as well.

Comment 6 Ondřej Pražák 2019-11-19 11:54:25 UTC

Created redmine issue https://projects.theforeman.org/issues/28300 from this bug

Comment 7 Bryan Kearney 2020-03-04 14:08:43 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 8 Bryan Kearney 2020-04-02 12:34:24 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.