Bug 1078200 - Unable to create a volume with bricks in the root partition for 3.3 clusters
Summary: Unable to create a volume with bricks in the root partition for 3.3 clusters
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-webadmin
Version: 3.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.4.3
Assignee: Kanagaraj
QA Contact: Pavel Stehlik
URL:
Whiteboard: gluster
Depends On: 1051696
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-19 11:40 UTC by Sahina Bose
Modified: 2016-04-18 10:06 UTC (History)
16 users (show)

Fixed In Version:
Clone Of: 1051696
Environment:
Last Closed: 2014-06-23 11:33:22 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)

Description Sahina Bose 2014-03-19 11:40:13 UTC
+++ This bug was initially created as a clone of Bug #1051696 +++

Description of problem:

On a 3.3 cluster with gluster 3.4 nodes added, an error message is given when a user tries to create a volume with bricks in the root partition. The error message implies that there is a force option which isn't present; from the gui there is no way to create a volume with bricks in the root partition in a 3.3 cluster


Steps to Reproduce:
1. create a 3.3 cluster
2. add gluster 3.4 nodes to the cluster
3. create a volume using bricks in the root partition
for example /tmp/brick1

Actual results:

error message is prompted to user 
"Error while executing action Create Gluster Volume: Volume create failed
error: The brick vm10_lab_eng_blr_redhat_com:/home/test is is being created in the root partition_ It is recommended that you don't use the system's root partition for storage backend_ Or use 'force' at the end of the command if you want to override this behavior_
return code: 115"
user is unable to create a volume with bricks in the root partition


Expected results:

oVirt should allow creation of bricks in the root partition without prompting to be consistent with 3.2 clusters of 2.1 nodes and 3.2 clusters of 2.1u1 nodes.

Comment 1 Sandro Bonazzola 2014-03-28 09:14:35 UTC
Re-targeting to 3.3.5 since 3.3.4 has been released

Comment 2 Sandro Bonazzola 2014-04-04 09:00:24 UTC
Re-targeting to 3.4.1 since 3.3.5 RC has been released and this is not marked as blocker.

Comment 3 Sandro Bonazzola 2014-05-08 13:50:46 UTC
This is an automated message.

oVirt 3.4.1 has been released.
This issue has been retargeted to 3.4.2 as it has priority high, please retarget if needed.
If this is a blocker please add it to the tracker Bug #1095370

Comment 4 Sandro Bonazzola 2014-06-11 07:04:59 UTC
This is an automated message:
oVirt 3.4.2 has been released.
This bug has been re-targeted from 3.4.2 to 3.4.3 since priority or severity were high or urgent.

Comment 5 Sandro Bonazzola 2014-06-11 07:05:33 UTC
This is an automated message:
oVirt 3.4.2 has been released.
This bug has been re-targeted from 3.4.2 to 3.4.3 since priority or severity were high or urgent.

Comment 6 Sahina Bose 2014-06-23 11:33:22 UTC
Since this is a change in gluster behaviour, this behaviour needs to be documented.

In 3.3 cluster, passing a force option to vdsm by default is not possible as the older vdsm will not support this option.

Marking this bug as CANTFIX


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