Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1364947 - [downstream clone][RFE] - Deactivate storage domain only if ovf store was updated
[downstream clone][RFE] - Deactivate storage domain only if ovf store was upd...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine (Show other bugs)
unspecified
Unspecified Unspecified
medium Severity high
: ovirt-4.2.0
: ---
Assigned To: Eyal Shenitzky
Yosi Ben Shimon
: FutureFeature
: 1477147 (view as bug list)
Depends On: 1321585 1523225
Blocks:
  Show dependency treegraph
 
Reported: 2016-08-08 05:28 EDT by rhev-integ
Modified: 2018-05-15 13:40 EDT (History)
19 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
In the current release, the storage domain is prevented from going into maintenance if the OVF update fails. An optional check box to force maintenance mode, if desired, has been added.
Story Points: ---
Clone Of: 1321585
Environment:
Last Closed: 2018-05-15 13:38:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Storage
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
ratamir: testing_plan_complete-


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 83368 None None None 2017-11-26 09:33 EST
oVirt gerrit 83383 None None None 2017-11-26 09:35 EST
oVirt gerrit 83437 None None None 2017-11-26 09:34 EST
Red Hat Product Errata RHEA-2018:1488 None None None 2018-05-15 13:40 EDT

  None (edit)
Comment 10 Marina 2016-10-05 13:48:00 EDT
I am changing this from RFE to a bug and setting the proper flags.
This is a flaw in the design and can lead into data loss on customer setups.
Comment 12 Allon Mureinik 2016-10-05 16:48:06 EDT
(In reply to Marina from comment #10)
> I am changing this from RFE to a bug and setting the proper flags.
> This is a flaw in the design and can lead into data loss on customer setups.

Hardly.
Please share a sensible reproduction to this issue - deleting the OVF store isn't something anyone should do.
Until then, targeting to a more appropriate version than 4.0.z.
Comment 14 Germano Veit Michel 2016-10-13 02:26:39 EDT
It's not only preventing to Detach/Deactivate if the OVFs updated. All the images must be in healthy condition before detaching, see BZ 1384321.
Comment 16 Marina 2016-10-31 12:26:08 EDT
Allon, do I understand correctly that OVF store should be updated once detach(maintenance?) command is issued? If this is the flow, then I think the problem is that for some reason the update didn't happen before detaching and the information was lost.

I do not think this bug is about preventing SD detachment while performing the update, but detaching it without having the updated information pushed to the OVF store on the domain.
Comment 17 Julio Entrena Perez 2016-11-01 10:33:16 EDT
(In reply to Marina from comment #16)
> but detaching it without having the updated information pushed
> to the OVF store on the domain.
That's correct.
Comment 23 Allon Mureinik 2017-09-12 08:37:13 EDT
This depends on an RFE that currently isn't targeted for 4.2 - pushing out.
Yaniv L, if you disagree, let's discuss and see if this RFE should be brought into 4.2.
Comment 27 Allon Mureinik 2017-11-23 07:38:35 EST
Eyal - what's the status here? The BZ is in post, but I see no patches attached to it.
Comment 28 Yaniv Lavi 2017-11-26 07:25:30 EST
*** Bug 1477147 has been marked as a duplicate of this bug. ***
Comment 30 Yosi Ben Shimon 2018-01-21 09:15:06 EST
Eyal, can we move this bug to VERIFIED based on 
https://bugzilla.redhat.com/show_bug.cgi?id=1523225#c7 ?
Comment 31 Eyal Shenitzky 2018-01-22 01:50:30 EST
Yes.
Comment 32 Yosi Ben Shimon 2018-01-22 06:19:19 EST
OK.
Moving to VERIFIED.
Comment 38 errata-xmlrpc 2018-05-15 13:38:43 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHEA-2018:1488

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