+++ This bug was initially created as a clone of Bug #1210841 +++ Description of problem: Extended partition is shown as available for bricks creation, however when someone wants to create a brick on such partition it fails with unexpected exception. Version-Release number of selected component (if applicable): ovirt-engine-3.6.0-0.0 How reproducible: 100% Steps to Reproduce: 1. Create some extended partition on host 2. Go to 'Storage Device' tab check availability of the partition and try to create a brick on it Actual results: Unexpected exception Expected results: The partition should not be available it should be shown with a lock or add some functionality which creates a proper logical partition first. Additional info: --- Additional comment from Lubos Trilety on 2015-04-10 12:59:07 EDT --- Such partition stays to be shown as available even when it is completely used.
Marking it as low priority as extended partition is not a common use case for gluster.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
To align with BZ 1270792, I would propose to disallow admin to create brick on extended partition.
this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015. Please review this bug and if not a blocker, please postpone to a later release. All bugs not postponed on GA release will be automatically re-targeted to - 3.6.1 if severity >= high - 4.0 if severity < high
oVirt 3.6.0 has been released on November 4th, re-targeting to 4.0 since this bug has been marked with severity < high
This bug is flagged for 3.6, yet the milestone is for 4.0 version, therefore the milestone has been reset. Please set the correct milestone or add the flag.
(In reply to Martin Bukatovic from comment #3) > To align with BZ 1270792, I would propose to disallow admin to create brick > on > extended partition. Brick creation should be blocked on any partitions not just extended partition. Changing the bug description accordingly.
This bug is not marked for z-stream, yet the milestone is for a z-stream version, therefore the milestone has been reset. Please set the correct milestone or add the z-stream flag.
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
oVirt 4.0 beta has been released, moving to RC milestone.
Considering this is not a regular scenario to create a MBR partition and trying to create brick on top of it, I would propose to close this bug as won't fix. Kasturi, please let me know if you have any objects for closing this bug as won't fix.
(In reply to Ramesh N from comment #12) > Considering this is not a regular scenario to create a MBR partition and > trying to create brick on top of it, I would propose to close this bug as > won't fix. Exactly, this is not a valid scenario which would break data alignment and for that reason, it would make sense to prevent admin to configure bricks in this way by mistake.
yes, you can close this bug.
(In reply to Martin Bukatovic from comment #13) > (In reply to Ramesh N from comment #12) > > Considering this is not a regular scenario to create a MBR partition and > > trying to create brick on top of it, I would propose to close this bug as > > won't fix. > > Exactly, this is not a valid scenario which would break data alignment and > for that reason, it would make sense to prevent admin to configure bricks > in this way by mistake. Exactly, +1
Low priority, closing