Bug 1664748 - [CinderLib] - remove and format managed storage via webadmin fails - Failed to FormatStorageDomainVDS, error = Storage domain does not exist
Summary: [CinderLib] - remove and format managed storage via webadmin fails - Failed ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.3.0
: ---
Assignee: Tal Nisan
QA Contact: Avihai
URL:
Whiteboard:
Depends On:
Blocks: 1539837
TreeView+ depends on / blocked
 
Reported: 2019-01-09 15:07 UTC by Avihai
Modified: 2019-02-13 07:43 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-13 07:43:23 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.3+


Attachments (Terms of Use)
Video of the issue (1.02 MB, video/mp4)
2019-01-09 15:07 UTC, Avihai
no flags Details
engine log and rpms.txt (68.68 KB, application/gzip)
2019-01-09 15:08 UTC, Avihai
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 96852 0 master MERGED core: prevent from formatting managed block storage domain 2019-01-13 14:36:55 UTC

Description Avihai 2019-01-09 15:07:46 UTC
Created attachment 1519519 [details]
Video of the issue

Description of problem:
Via Webadmin try to remove and format an existing unattached managed storage domain -> action failed with "Failed to FormatStorageDomainVDS, error = Storage domain does not exist"

Engine:
2019-01-09 17:01:51,707+02 INFO  [org.ovirt.engine.core.bll.storage.domain.RemoveStorageDomainCommand] (default task-9) [3323399c-f7ab-4898-ae5b-aca876b6c5d6] Lock Acquired to object 'EngineLock:{exclusiveLocks='[90bd245e-f4e6-446c-8177-e3cf07c12785=STORAGE]', sharedLocks=''}'
2019-01-09 17:01:51,725+02 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetStorageDomainInfoVDSCommand] (default task-9) [3323399c-f7ab-4898-ae5b-aca876b6c5d6] START, HSMGetStorageDomainInfoVDSCommand(HostName = host_mixed_3, HSMGetStorageDomainInfoVDSCommandParameters:{hostId='2f080837-cf46-461b-9fb1-9d08afc103d1', storageDomainId='90bd245e-f4e6-446c-8177-e3cf07c12785'}), log id: 2d04bc22
2019-01-09 17:01:52,426+02 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetStorageDomainInfoVDSCommand] (default task-9) [3323399c-f7ab-4898-ae5b-aca876b6c5d6] Failed in 'HSMGetStorageDomainInfoVDS' method
2019-01-09 17:01:52,442+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-9) [3323399c-f7ab-4898-ae5b-aca876b6c5d6] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM host_mixed_3 command HSMGetStorageDomainInfoVDS failed: Storage domain does not exist: (u'90bd245e-f4e6-446c-8177-e3cf07c12785',)


Version-Release number of selected component (if applicable):
Software Version:4.3.0-0.4.master.20190106162157.gitd96a412.el7


How reproducible:
100%

Steps to Reproduce:
1. Via Webadmin/REST create a managed storage domain.
2. Via Webadmin try to remove and format an existing unattached managed storage domain 

Actual results:
action failed with "Failed to FormatStorageDomainVDS, error = Storage domain does not exist"

Expected results:
Action should succeed or at least block the option to format the managed storage domain.

Additional info:

Comment 1 Avihai 2019-01-09 15:08:21 UTC
Created attachment 1519520 [details]
engine log and rpms.txt

Comment 2 Sandro Bonazzola 2019-01-28 09:34:37 UTC
This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

Comment 3 Avihai 2019-02-03 13:16:31 UTC
Verified at 4.3.0.2-0.1.el7

Comment 4 Sandro Bonazzola 2019-02-13 07:43:23 UTC
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.0 release, it has been closed with a resolution of CURRENT RELEASE.

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


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