Bug 850439 - Guide me should be disabled for local DC -> local cluster
Summary: Guide me should be disabled for local DC -> local cluster
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Alexey Chub
QA Contact: Jiri Belka
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-21 15:17 UTC by Doron Fediuck
Modified: 2016-02-10 19:35 UTC (History)
10 users (show)

Fixed In Version: si23
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-04 20:04:18 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Guide-me dialog of an existing local cluster. (34.72 KB, image/png)
2012-08-21 15:17 UTC, Doron Fediuck
no flags Details

Description Doron Fediuck 2012-08-21 15:17:02 UTC
Created attachment 605965 [details]
Guide-me dialog of an existing local cluster.

Description of problem:
Once you configure a local cluster, the guide-me button has no point,
since nothing can be done in this dialog.

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

How reproducible:
Use the guide me on a configured local cluster.
See the attached.

Steps to Reproduce:
1. Have an existing local cluster that belongs to a local DC.
2. Push the guide me button for this cluster.
  
Actual results:
See everything disabled, and a meaningless "configure later" button to exit the dialog.

Expected results:
This dialog should not be accessible in this case.

Additional info:
The same issue happens when using the guide-me in a new system.
Once the host is selected for the new local cluster, everything is disabled,
and a meaningless "configure later" button to exit the dialog.
So I'd recommend to close the dialog after host selection happens in this
scenario.

Comment 2 Einav Cohen 2012-08-23 11:13:03 UTC
the "guide me" for local cluster is the only one with potential to contain no possible additional actions: Once a local cluster has a host, you cannot add more hosts to it, therefore there is no action available via the "guide me" dialog.

[in other "guide-me"s, there is always something that can be done: in a regular cluster, you can always add another host, in DC guide-me you can always add another SD, in VM guide-me you can always add another disk/nic, etc.]

need to consult graphic designer in order to tweak the "guide-me" dialog for that special case (e.g. put a comment of "nothing more to configure", put "close" button instead of "configure later" button, etc.)

Comment 3 Barak 2012-08-30 15:39:32 UTC
Einav - please provide answer from the graphic designer

Comment 4 Einav Cohen 2012-08-31 07:54:37 UTC
answer from graphic designer:
If the entity is fully configured and there is nothing else to do with it (e.g. "guide me" for local-cluster that already has Hosts in it), simply show a regular, simple dialog (like a CanDoAction/Error dialog, only with no Error texts or icons...) with text phrased like the following:
"The Cluster is fully configured and ready for use."
Dialog should contain only an "OK" button.

Comment 5 Alexey Chub 2012-10-02 11:20:03 UTC
Change-Id: I594e6721ea114560784152dcdd5d85910f50b34e

Comment 6 Oded Ramraz 2012-10-10 08:50:40 UTC
Guide me button is still available for local storage DC / Cluster. 
Tested with si20

Comment 7 Alexey Chub 2012-10-16 13:41:16 UTC
Change-Id: I16d72904dfebe8fa0a29065e587c829998da782f
http://gerrit.ovirt.org/#/c/8435/

Comment 8 Alexey Chub 2012-10-28 10:26:00 UTC
Relates to this issue:
Change-Id: Idd623481d0eb77bfbaa1e8b3eec8b445020711c8

Comment 9 Yair Zaslavsky 2012-10-28 14:17:10 UTC
Merged -

60000cbfe5b06ea199c9d346a51c14a44a384a70

And

aee29f7e001b4e05642255c08187fc8cf36be95

Comment 10 Jiri Belka 2012-11-08 14:38:21 UTC
OK,

- tested with SI24
- after adding a host to 'Local Storage' DC the 'Guide Me' shows 'The Cluster is fully configured and ready for use.' as clarified in comment #4.


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