Bug 1673319 - [CinderLib] failed updating managed block storage - in 'SetStorageDomainDescriptionVDS'
Summary: [CinderLib] failed updating managed block storage - in 'SetStorageDomainDescr...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.3.1
: ---
Assignee: Eyal Shenitzky
QA Contact: Shir Fishbain
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-07 11:27 UTC by Eyal Shenitzky
Modified: 2019-03-13 16:40 UTC (History)
3 users (show)

Fixed In Version: ovirt-engine-4.3.1.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-13 16:40:30 UTC
oVirt Team: Storage
aoconnor: ovirt-4.3+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 97627 0 master MERGED core: avoid updating MBS domain description in VDSM 2019-02-07 21:10:35 UTC

Description Eyal Shenitzky 2019-02-07 11:27:28 UTC
Description of problem:

Updating managed block storage domain faild on 'SetStorageDomainDescriptionVDS':

2019-02-07 13:17:48,639+02 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.SetStorageDomainDescriptionVDSCommand] (default task-1) [d780b8f9-8bab-4e5d-8f69-a02f992e9361] Failed in 'SetStorageDomainDescriptionVDS' method
2019-02-07 13:17:48,676+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-1) [d780b8f9-8bab-4e5d-8f69-a02f992e9361] EVENT_ID: IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command SetStorageDomainDescriptionVDS failed: Storage domain does not exist: ('02b10c38-06a6-454f-b490-b2dd182ec0b5',)
2019-02-07 13:17:48,679+02 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (default task-1) [d780b8f9-8bab-4e5d-8f69-a02f992e9361] IrsBroker::Failed::SetStorageDomainDescriptionVDS: IRSGenericException: IRSErrorException: Failed to SetStorageDomainDescriptionVDS, error = Storage domain does not exist: ('02b10c38-06a6-454f-b490-b2dd182ec0b5',), code = 358
2019-02-07 13:17:48,716+02 INFO  [org.ovirt.engine.core.vdsbroker.irsbroker.SetStorageDomainDescriptionVDSCommand] (default task-1) [d780b8f9-8bab-4e5d-8f69-a02f992e9361] FINISH, SetStorageDomainDescriptionVDSCommand, return: , log id: 2bc894ed
2019-02-07 13:17:48,718+02 ERROR [org.ovirt.engine.core.bll.storage.domain.UpdateStorageDomainCommand] (default task-1) [d780b8f9-8bab-4e5d-8f69-a02f992e9361] Command 'org.ovirt.engine.core.bll.storage.domain.UpdateStorageDomainCommand' failed: EngineException: org.ovirt.engine.core.vdsbroker.irsbroker.IRSErrorException: IRSGenericException: IRSErrorException: Failed to SetStorageDomainDescriptionVDS, error = Storage domain does not exist: ('02b10c38-06a6-454f-b490-b2dd182ec0b5',), code = 358 (Failed with error StorageDomainDoesNotExist and code 358)
2019-02-07 13:17:48,744+02 ERROR [org.ovirt.engine.core.bll.storage.domain.UpdateStorageDomainCommand] (default task-1) [d780b8f9-8bab-4e5d-8f69-a02f992e9361] Transaction rolled-back for command 'org.ovirt.engine.core.bll.storage.domain.UpdateStorageDomainCommand'.


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

How reproducible:
100%

Steps to Reproduce:
1. Create managed block storage
2. From the UI - try to update the domain name


Actual results:
Operation failed with the above error

Expected results:
Storage domain name should be updated

Additional info:

Comment 1 Shir Fishbain 2019-03-07 16:44:11 UTC
Verified

The 3 Cinderlib SD for hp3par, Kaminario, and Netapp were updated.

Cinderlib version: 0.3.9
vdsm-4.30.9-1.el7ev.x86_64
ovirt-engine-4.3.1.1-0.1.el7.noarch

Comment 2 Sandro Bonazzola 2019-03-13 16:40:30 UTC
This bugzilla is included in oVirt 4.3.1 release, published on February 28th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.1 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.