Bug 1287589

Summary: Wrong JSON format in AutoRecoveryAllowedTypes config value
Product: [oVirt] ovirt-engine Reporter: Eli Mesika <emesika>
Component: Backend.CoreAssignee: Eli Mesika <emesika>
Status: CLOSED CURRENTRELEASE QA Contact: Gonza <grafuls>
Severity: high Docs Contact:
Priority: high    
Version: 3.6.0CC: bugs, emesika, oourfali
Target Milestone: ovirt-3.6.1Flags: oourfali: ovirt-3.6.z?
oourfali: blocker?
rule-engine: planning_ack?
rule-engine: devel_ack+
pstehlik: testing_ack+
Target Release: 3.6.1.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-19 15:37:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eli Mesika 2015-12-02 11:48:51 UTC
Description of problem:

AutoRecoveryAllowedTypes config key value is  {\"storage domains\":\"true\",\"hosts\":\"true\"}

This is not a legal JSON format and generates the following error upon application start:

 ERROR [org.ovirt.engine.core.dal.dbbroker.generic.DBConfigUtils] (ServerService Thread Pool -- 43) [] Error parsing option 'AutoRecoveryAllowedTypes' value: org.codehaus.jackson.JsonParse
Exception: Unexpected character ('\' (code 92)): was expecting double-quote to start field name
 at [Source: java.io.StringReader@3198de41; line: 1, column: 3]


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


How reproducible:
Always

Steps to Reproduce:
1.Start application and check engine.log 
2.
3.

Actual results:

Application aborted on illegal configuration value 

Expected results:

Value should be fixed to a legal JSON value and no error generated for this key upon application start 

Additional info:

Comment 1 Red Hat Bugzilla Rules Engine 2015-12-02 11:58:59 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 2 Red Hat Bugzilla Rules Engine 2015-12-02 12:01:12 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 3 Sandro Bonazzola 2015-12-10 12:42:08 UTC
This bug is referenced in ovirt-engine 3.6.1.2 git log.
Please check if the BZ is ready to be moved to QE and set target release accordingly.

Comment 4 Gonza 2016-01-14 11:18:45 UTC
Verified with:
rhevm-3.6.2-0.1.el6.noarch

No ERROR msgs on eninge.log about AutoRecoveryAllowedTypes.