Bug 1459616 - State of virtual system is still 'unknown'
Summary: State of virtual system is still 'unknown'
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Server
Version: 580
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jiří Dostál
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: sat58-errata
TreeView+ depends on / blocked
 
Reported: 2017-06-07 15:13 UTC by Jiří Dostál
Modified: 2017-07-20 11:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-20 11:40:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.