Bug 1287540 - [Admin Portal] List of problematic clusters missing in operation failure dialog (edit DC - bump up compat level)
Summary: [Admin Portal] List of problematic clusters missing in operation failure dial...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 3.6.1
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ovirt-4.1.0-alpha
: 4.1.0.2
Assignee: Phillip Bailey
QA Contact: Jiri Belka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-02 10:13 UTC by Jiri Belka
Modified: 2023-09-14 03:14 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-02-01 14:55:36 UTC
oVirt Team: SLA
Embargoed:
rule-engine: ovirt-4.1+
rule-engine: planning_ack+
dfediuck: devel_ack+
lsvaty: testing_ack+


Attachments (Terms of Use)
screenshot (137.14 KB, image/png)
2015-12-02 10:13 UTC, Jiri Belka
no flags Details
New version of error message (15.18 KB, image/png)
2016-08-08 20:50 UTC, Phillip Bailey
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 62091 0 master MERGED webadmin: Edit error message in DC operation failure dialog 2016-08-09 07:16:39 UTC
oVirt gerrit 64259 0 ovirt-engine-4.0 MERGED webadmin: Edit error message in DC operation failure dialog 2016-09-29 08:57:54 UTC

Description Jiri Belka 2015-12-02 10:13:01 UTC
Created attachment 1101393 [details]
screenshot

Description of problem:
List of problematic clusters missing in operation failure dialog (edit DC - bump up compat level).

When one tries to bump up compat level of a DC and the DC has at least one cluster with lower cluster level than desired compat level of the DC, the operation fails and there's an error dialog which states:

~~~
Operation Canceled
Error while executing action: Cannot update Data Center compatibility version to a value that is greater than its Cluster's version. The following clusters should be upgraded new.
~~~

But as you can see there's now list of "following clusters" in the dialog (see screenshot). I would also say that "Cluster's" should be lowercase as this is not refering to name or special object (maintab...).

Version-Release number of selected component (if applicable):
rhevm-3.6.1-0.2.el6.noarch

How reproducible:
100%

Steps to Reproduce:
1. have 3.6.x engine
2. (you need to decrease to 3.5 if using Default) DC 3.5 compact level, 
   cluster1 3.6 level, cluster2 3.5 level
3. edit DC and bump-up compat level to 3.6

Actual results:
operation failure dialog states there should be a cluster list but there's none

Expected results:
either change the sentence or show the list of "problematic" clusters in the
dialog

Additional info:

Comment 1 Yaniv Kaul 2015-12-03 08:24:43 UTC
I'm also unsure what the word 'new' means in that dialog box.

Comment 2 Sandro Bonazzola 2016-01-14 07:30:32 UTC
Roy, can you take a look?

Comment 3 Sandro Bonazzola 2016-03-11 14:41:16 UTC
Doron, I see you targeted this bug to 3.6.6 but it is blocking bug #1285700 which is targeted to 3.6.5. Can this be fixed in 3.6.5 or should we postpone bug #1285700 ?

Comment 4 Sandro Bonazzola 2016-04-06 11:13:31 UTC
dropping block on bug #1285700 since this bug has been targeted to 4.1.

Comment 5 Phillip Bailey 2016-08-08 20:50:52 UTC
Created attachment 1188911 [details]
New version of error message

Comment 6 Phillip Bailey 2016-08-08 20:54:26 UTC
I didn't see where the list was being omitted. I made the capitalization correction and added a colon between the message and the list. I have attached a screenshot of the new message.

Are you sure that the "new" in the original screenshot wasn't the name of the problematic cluster?

Comment 7 Jiri Belka 2016-08-08 22:38:48 UTC
(In reply to Phillip Bailey from comment #6)
> I didn't see where the list was being omitted. I made the capitalization
> correction and added a colon between the message and the list. I have
> attached a screenshot of the new message.
> 
> Are you sure that the "new" in the original screenshot wasn't the name of
> the problematic cluster?

I can't be sure what was 8 months ago. Move it to ON_QA at least for colon verification ;)

Comment 8 Sandro Bonazzola 2016-12-12 10:57:14 UTC
This bug is targeted 4.1 but it appears that the fix has been included in ovirt-engine-4.0.6.3. Please crosscheck and re-target if it's fixed in 4.0.6.

Comment 9 Sandro Bonazzola 2016-12-12 13:59:52 UTC
The fix for this issue should be included in oVirt 4.1.0 beta 1 released on December 1st. If not included please move back to modified.

Comment 10 Jiri Belka 2017-01-11 14:17:46 UTC
ok, ovirt-engine-webadmin-portal-4.1.0-0.3.beta2.el7.noarch


Error while executing action: Cannot update Data Center compatibility version to a value that is greater than its cluster's version. The following clusters should be upgraded: test.

Comment 11 Red Hat Bugzilla 2023-09-14 03:14:11 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


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