Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1459616

Summary:	State of virtual system is still 'unknown'
Product:	Red Hat Satellite 5	Reporter:	Jiří Dostál <jdostal>
Component:	Server	Assignee:	Jiří Dostál <jdostal>
Status:	CLOSED NOTABUG	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	580	CC:	tlestach
Target Milestone:	---
Target Release:	---
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:	2017-07-20 11:40:22 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:
Bug Depends On:
Bug Blocks:	1450111

Description Jiří Dostál 2017-06-07 15:13:39 UTC

Description of problem:
When listing virtual systems on 'rhn/systems/VirtualList.do', state of a system is always 'unknown', no matter whether the system is running or not.

Possible values should be:
rhnschema=# select name from rhnvirtualinstancestate;
  name   
---------
 Unknown
 Running
 Stopped
 Crashed
 Paused
(5 rows)


Version-Release number of selected component (if applicable):
Satellite 5.x, Spacewalk

How reproducible:
Always

Steps to Reproduce:
1. Register some virtual systems to Satellite
2. Go to '$FQDN/rhn/systems/VirtualList.do'
3. Check system state

Actual results:
Always 'unknown', independent on real state 

Expected results:
Reflect real status (running or not)

Additional info:
This bug was found during verification of #1356106. Until then, the servername was shown instead state, so the behavior was hidden.

Comment 1 Jiří Dostál 2017-07-20 11:40:22 UTC

I've tried different scenarios and came up with following - It is not a bug, as the status is correctly displayed when the virtual system has its hypervisor registered to same Satellite. Steps to (not)reproduce:

1) Create a kickstart profile for virtual system
2) Schedule kickstart of virtual system on some server
3) Wait for it to finish, check status in UI.

Result: Status is set correctly.