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

Bug 1467781

Summary: Can't import an existing block storage domain with Discard After Delete checked
Product: [oVirt] ovirt-engine Reporter: Idan Shaby <ishaby>
Component: BLL.StorageAssignee: Idan Shaby <ishaby>
Status: CLOSED CURRENTRELEASE QA Contact: Elad <ebenahar>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: amureini, bugs, mlipchuk
Target Milestone: ovirt-4.2.0Keywords: Regression
Target Release: ---Flags: rule-engine: ovirt-4.2+
rule-engine: blocker+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-20 11:46:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Idan Shaby 2017-07-05 06:55:23 UTC
Description of problem:
Since bug 1456414 was implemented, it's not possible to import an existing block storage domain using the UI with its default values (DAD = true).

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

How reproducible:
100%

Steps to Reproduce:
1. Import an existing block storage domain using the UI.
2. Don't change the DAD value (should be checked).

Actual results:
Fails with the error "Discard after delete is supported only by block domains".

Expected results:
Should work

Comment 1 Red Hat Bugzilla Rules Engine 2017-07-05 07:02:03 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 2 Elad 2017-07-19 07:58:19 UTC
Block based storage domain import succeeded without changing the discard after delete value (the default is true).

Tested via Webadmin using:
ovirt-engine-4.2.0-0.0.master.20170717104433.gita1ba045.el7.centos.noarch
vdsm-4.20.1-202.git9f953f3.el7.centos.x86_64

Comment 3 Sandro Bonazzola 2017-12-20 11:46:18 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.