Bug 889985 - [ovirt-engine] auto-recovery for storage server should change to "True", auto-recovery for hosts should be True by default on engine as in DB.
Summary: [ovirt-engine] auto-recovery for storage server should change to "True", auto...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.2.0
Hardware: x86_64
OS: Unspecified
urgent
high
Target Milestone: ---
: 3.2.0
Assignee: Liron Aravot
QA Contact: Dafna Ron
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-24 09:22 UTC by Haim
Modified: 2022-07-09 06:13 UTC (History)
10 users (show)

Fixed In Version: SF6
Doc Type: Enhancement
Doc Text:
Auto recovery for storage domains and hosts was not occuring by default. This was because the incorrect value of FALSE was set for storage domains auto recovery in the database, and hosts auto recovery in the engine. Auto recovery for both storage domains and hosts is now enabled by default. This has been done by: 1. Setting AutoRecoveryAllowedTypes as TRUE for storage domains. 2. Setting the correct value for AutoRecoveryAllowedTypes in ConfigValues.java.
Clone Of:
Environment:
Last Closed: 2013-06-10 21:30:46 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-47222 0 None None None 2022-07-09 06:13:07 UTC
Red Hat Product Errata RHSA-2013:0888 0 normal SHIPPED_LIVE Moderate: Red Hat Enterprise Virtualization Manager 3.2 update 2013-06-11 00:55:41 UTC
oVirt gerrit 10387 0 None MERGED core: enable auto recovery for storage domains 2020-05-20 14:44:15 UTC

Description Haim 2012-12-24 09:22:50 UTC
Description of problem:

currently, auto-recovery for storage domains is set on False:

 336 | AutoRecoveryAllowedTypes    | {"storage domains":"false","hosts":"true"} | general

please change it to True as we have supported code which requires this change.

Comment 3 Liron Aravot 2013-01-03 13:26:29 UTC
http://gerrit.ovirt.org/#/c/10387/

1. set AutoRecoveryAllowedTypes as true for storage domains.
2. set the correct value for AutoRecoveryAllowedTypes in
ConfigValues.java so that auto recovery will be enabled for hosts as
configured in vdc_options table without having to reload it.

Comment 4 Leonid Natapov 2013-02-13 14:53:30 UTC
SF6. fixed.

345 | AutoRecoveryAllowedTypes    | {"storage domains":"true","hosts":"true"} | general
(3 rows)

Comment 5 Cheryn Tan 2013-04-03 06:54:17 UTC
This bug is currently attached to errata RHEA-2013:14491. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.

* Consequence: What happens when the bug presents.

* Fix: What was done to fix the bug.

* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes

Thanks in advance.

Comment 6 errata-xmlrpc 2013-06-10 21:30:46 UTC
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.

http://rhn.redhat.com/errata/RHSA-2013-0888.html


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