Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1363954 - Missing columns name in hosts tab
Summary: Missing columns name in hosts tab
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: General
Hardware: Unspecified
OS: Unspecified
medium vote
Target Milestone: ---
: ---
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2016-08-04 06:47 UTC by meital avital
Modified: 2016-08-04 14:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2016-08-04 12:09:28 UTC
oVirt Team: UX
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)
screenshot (deleted)
2016-08-04 06:47 UTC, meital avital
no flags Details

System ID Priority Status Summary Last Updated
Red Hat Bugzilla 1308861 None None None Never

Internal Links: 1308861

Description meital avital 2016-08-04 06:47:08 UTC
Created attachment 1187363 [details]

Description of problem:Missing column name in host tab
In the hosts table, the second column is missing a name.
For example,  first column is showing host state, such as up, down, maintenance etc, but there is no name for that column.
and the second column is showing icons such as "update available" "HE crown" etc, but there is no name for this column also. 

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

How reproducible:

Steps to Reproduce:
1.Click on the hosts tab
2.The first and second columns are without column name.

Actual results:
columns name is missing 

Expected results:
Should be columns name

Additional info:
Also in VMs tab, storage tab and DC.
Please see attachment

Comment 1 Oved Ourfali 2016-08-04 12:09:28 UTC
This is as designed, used for different status icons.

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