Bug 1097685

Summary:	[RFE] Visualize pending registration in setup TUI
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Jiri Belka <jbelka>
Component:	RFEs	Assignee:	Andrew Cathrow <acathrow>
Status:	CLOSED NOTABUG	QA Contact:	Shai Revivo <srevivo>
Severity:	low	Docs Contact:
Priority:	medium
Version:	3.4.0	CC:	acathrow, bazulay, fdeutsch, gklein, iheim, lpeer, rbalakri, ycui, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	infra
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-15 12:08:22 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	875088, 1093884, 1135921, 1231379
Bug Blocks:

Description Jiri Belka 2014-05-14 10:27:14 UTC

Description of problem:
'Managed by: oVirt Engine $host' is visible even the host is in pending state, this seems odd.

What about this:

Managed by: oVirt Engine $host (pending)

...or:

Managed by: oVirt Engine $host
Status: pending

Version-Release number of selected component (if applicable):
Red Hat Enterprise Virtualization Hypervisor release 6.5 (20140513.0.el6ev)

How reproducible:
100%

Steps to Reproduce:
1. boot from pxe with management_server=$your_rhevm
2. check Status in rhevh tui
3.

Actual results:
the host is in RHEVM in pending state but RHEVH Status tab shows it is managed by RHEVM. Well... not yet.

Expected results:
Either do not lie in this time or distinguish that it is pending for approval be to Managed by...

Additional info:
I doubt about sense of current

'Status: Virtualization hardware was detected and is enabled'

Who cares about it? I think installation should fail completely if host HW is not good enough for being RHEV host :)

Comment 1 Douglas Schilling Landgraf 2014-05-20 22:01:17 UTC

Hi Fabian,

Any suggestion to handle this one? I would suggest that this report might require BZ#1093884. What do you say?


> 'Status: Virtualization hardware was detected and is enabled'
> 
> Who cares about it? I think installation should fail completely if host HW
> is not good enough for being RHEV host :)

Users can enable virtualization in the host if it's disable in the BIOS after installation.

Comment 2 Fabian Deutsch 2014-05-21 12:51:33 UTC

(In reply to Douglas Schilling Landgraf from comment #1)
> Hi Fabian,
> 
> Any suggestion to handle this one? I would suggest that this report might
> require BZ#1093884. What do you say?

No, no suggestions. But IMO the referenced bug above is the right direction. 
IIUIC the information is currently not available (if registeration is pending), thus: Before we can expose/use this information in the UI it needs to be made available, which needs to be handled by vdsm-reg or it's successor - or whatever component.

And further more - the vdsm_reg rewrite is currently targeted upstream for 3.5.

Comment 3 Douglas Schilling Landgraf 2014-05-21 13:59:34 UTC

(In reply to Fabian Deutsch from comment #2)
> (In reply to Douglas Schilling Landgraf from comment #1)
> > Hi Fabian,
> > 
> > Any suggestion to handle this one? I would suggest that this report might
> > require BZ#1093884. What do you say?
> 
> No, no suggestions. But IMO the referenced bug above is the right direction. 
> IIUIC the information is currently not available (if registeration is
> pending), thus: Before we can expose/use this information in the UI it needs
> to be made available, which needs to be handled by vdsm-reg or it's
> successor - or whatever component.

Thanks Fabian, I do believe if ovirt-engine expose this data and any component can consult without authentication we could do it directly in ovirt-node-plugin-vdsm.