Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1287540

Summary: [Admin Portal] List of problematic clusters missing in operation failure dialog (edit DC - bump up compat level)
Product: [oVirt] ovirt-engine Reporter: Jiri Belka <jbelka>
Component: Frontend.WebAdminAssignee: Phillip Bailey <phbailey>
Status: CLOSED CURRENTRELEASE QA Contact: Jiri Belka <jbelka>
Severity: low Docs Contact:
Priority: low    
Version: 3.6.1CC: bugs, dfediuck, gklein, jbelka, lsvaty, phbailey, sbonazzo
Target Milestone: ovirt-4.1.0-alphaFlags: rule-engine: ovirt-4.1+
rule-engine: planning_ack+
dfediuck: devel_ack+
lsvaty: testing_ack+
Target Release: 4.1.0.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: A lack of clear delineation between the error message text and list of problematic clusters made it difficult to know whether the list of clusters was being shown properly. Consequence: Users could potentially be confused by the error message, making it difficult for them to correct the underlying problem. Fix: To clearly define the error message text from the problematic cluster list, a colon was added after the message text. Result: The end of the message text and beginning of the problematic clusters list should be clear to users, avoiding the potential of confusion.
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-01 14:55:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: SLA RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot
none
New version of error message none

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