Bug 1045612 - [RHSC] Change Message "Error while executing action: Cannot decrease data center compatibility version"
Summary: [RHSC] Change Message "Error while executing action: Cannot decrease data cen...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: rhsc
Version: 2.1
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Kanagaraj
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-20 20:43 UTC by Matt Mahoney
Modified: 2016-04-18 10:07 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-03 17:11:24 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Matt Mahoney 2013-12-20 20:43:18 UTC 
Description of problem:
When attempting to decrease the Cluster compatibility version from 3.3 to 3.2, the following message is rendered:

Error while executing action: Cannot decrease data center compatibility version

Data Center should be removed from message.

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

How reproducible:
Always

Steps to Reproduce:
1. Create a 3.3 cluster
2. Attempt to change the cluster version to 3.2
3.

Actual results:
Data Center reference in message.

Expected results:
Reference to Data Center should be removed from the message.

Additional info:
Comment 2 Dusmant 2014-04-01 05:20:43 UTC 
Triaged and not taken in Denali
Comment 3 Vivek Agarwal 2015-12-03 17:11:24 UTC 
Thank you for submitting this issue for consideration in Red Hat Gluster Storage. The release for which you requested us to review, is now End of Life. Please See https://access.redhat.com/support/policy/updates/rhs/

If you can reproduce this bug against a currently maintained version of Red Hat Gluster Storage, please feel free to file a new report against the current release.
Note You need to log in before you can comment on or make changes to this bug.