Bug 1477147 - [RFE] Provide a warning message while detaching storage domain with illegal OVF_STORE
Summary: [RFE] Provide a warning message while detaching storage domain with illegal O...
Keywords:
Status: CLOSED DUPLICATE of bug 1364947
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.1.4
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-01 10:49 UTC by nijin ashok
Modified: 2020-09-10 11:05 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-26 12:25:30 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:
lsvaty: testing_plan_complete-


Attachments (Terms of Use)

Description nijin ashok 2017-08-01 10:49:30 UTC
Description of problem:

The OVF_STORE disk creation can fail and below messages will be logged in the audit log if it fails.

==
The Disk with the id might be removed manually for automatic attempt to create new one. OVF updates won't be attempted on the created disk.
==

This may get unnoticed by the user. In a later stage, the administrator may detach the storage domain without noticing an illegal OVF_STORE. However, no warnings are shown while detaching the storage domain with illegal OVF_STORE. So the user will end up with only disks and no VMs if we attach the storage domain again.


Actual results:

No warnings to user if he detach a storage domain with illegal OVF_STORE

Expected results:

Provide a warning message that the user will not be able to import the VMs since there is no OVF_STORE with VM info.

Additional info:

Comment 1 Yaniv Kaul 2017-08-01 12:18:14 UTC
Do we have a separate bug on why the OVF failed?

Comment 2 nijin ashok 2017-08-02 17:23:29 UTC
(In reply to Yaniv Kaul from comment #1)
> Do we have a separate bug on why the OVF failed?

The OVF failed with sanlock error. But there are no valid error messages in sanlock log or in exception message why it actually failed. I have opened the BUG 1477717 specific for this.

Comment 3 Yaniv Lavi 2017-11-26 12:25:30 UTC

*** This bug has been marked as a duplicate of bug 1364947 ***


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