Bug 1532630 - Prevent deactivation of a data domain with ISO disks that are attached to running VMs
Summary: Prevent deactivation of a data domain with ISO disks that are attached to run...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: future
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-4.2.1
: ---
Assignee: Tal Nisan
QA Contact: Avihai
URL:
Whiteboard:
Depends On: 1536826
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-09 13:21 UTC by Tal Nisan
Modified: 2018-02-22 10:02 UTC (History)
2 users (show)

Fixed In Version: ovirt-engine-4.2.1.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-22 10:02:05 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.2+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 86119 0 master MERGED core: Prevent deactivating domain with ISO attached to running VMs 2018-01-10 09:23:26 UTC

Description Tal Nisan 2018-01-09 13:21:05 UTC 
Description of problem:
Since ISOs can now reside on data domains rather than only on a designated ISO domains, moving a storage domain to maintenance should be forbidden in case the domain contains ISO images that are connected to running VMs
Comment 1 Avihai 2018-02-19 12:56:05 UTC 
verified on engine 4.2.2-0.1.

Snippet from engine log - should '$VmNames' be there?

2018-02-19 14:50:22,960+02 WARN  [org.ovirt.engine.core.bll.storage.domain.DeactivateStorageDomainWithOvfUpdateCommand] (default task-20) [76fc633c-9879-47b4-96bf-437553219fe1] Validation of action 'DeactivateSt
orageDomainWithOvfUpdate' failed for user admin@internal-authz. Reasons: VAR__TYPE__STORAGE__DOMAIN,VAR__ACTION__DEACTIVATE,ERROR_CANNOT_DEACTIVATE_STORAGE_DOMAIN_WITH_ISO_ATTACHED,$VmNames vm1
Comment 2 Sandro Bonazzola 2018-02-22 10:02:05 UTC 
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018.

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