Bug 1000272 - Miss create "Data" logical volume when using the default value of "Data" in storage_vol_page
Summary: Miss create "Data" logical volume when using the default value of "Data" in s...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-node
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.4.1
Assignee: Ryan Barry
QA Contact: bugs@ovirt.org
URL:
Whiteboard: node
Depends On:
Blocks: 1022375
TreeView+ depends on / blocked
 
Reported: 2013-08-23 05:33 UTC by haiyang,dong
Modified: 2014-04-30 10:59 UTC (History)
13 users (show)

Fixed In Version:
Clone Of:
: 1022375 (view as bug list)
Environment:
Last Closed: 2014-04-30 10:59:54 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)
attached Screenshot (7.63 KB, image/png)
2013-08-23 05:33 UTC, haiyang,dong
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 19857 0 None None None Never

Description haiyang,dong 2013-08-23 05:33:11 UTC
Created attachment 789451 [details]
attached Screenshot

Description of problem:
boot ovirt-node-iso-3.1.0-0.999.999.20130822204541gitb3a1a44.284.fc18.iso, after enter into storage_vol_page,
didn't change any item values of storage_vol_page, just using the default values to partition.
But Miss create "Data" logical volume when using the default value of "Data" in  storage_vol_page(lvs.png)

no this issue when using custom "Data" value to create "Data" logical volume.

 


Version-Release number of selected component (if applicable):
ovirt-node-iso-3.1.0-0.999.999.20130822204541gitb3a1a44.284.fc18.iso

How reproducible:
100% 
 
Steps to Reproduce:

Actual result:
Miss create "Data" logical volume when using the default value of "Data" in  storage_vol_page

Expect result:
create "Data" logical volume  success when using the default value of "Data" in  storage_vol_page

Additional info:

Comment 1 Sandro Bonazzola 2014-03-04 09:22:09 UTC
This is an automated message.
Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.


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