Bug 1185818

Summary: [engine-backend] requests don't reach vdsm
Product: Red Hat Enterprise Virtualization Manager Reporter: rhev-integ
Component: vdsm-jsonrpc-javaAssignee: Piotr Kliczewski <pkliczew>
Status: CLOSED ERRATA QA Contact: Elad <ebenahar>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: bazulay, ebenahar, ecohen, eedri, fromani, gklein, iheim, juwu, laravot, lpeer, lsurette, oourfali, pkliczew, rbalakri, Rhev-m-bugs, sherold, smizrahi, yeylon, ylavi
Target Milestone: ---Keywords: Regression, ZStream
Target Release: 3.5.0-1   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: vt13.9 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1184454 Environment:
Last Closed: 2015-02-16 14:40:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1184454    
Bug Blocks:    

Comment 4 Yaniv Lavi 2015-01-27 13:11:46 UTC
what is the fixed version?

Comment 8 Julie 2015-02-02 00:53:53 UTC
If this bug requires doc text for errata release, please provide draft text in the doc text field in the following format:

Cause:
Consequence:
Fix:
Result:

The documentation team will review, edit, and approve the text.

If this bug does not require doc text, please set the 'requires_doc_text' flag to -.

Comment 9 Elad 2015-02-02 14:45:19 UTC
ActivateStorageDomain is performed as expected. Tested several times. Also tested a scenario I enountered previously in which I tried to put the master domain in maintenance while the other domain which supposed to take master is reported wrongly as Active while in fact it is not accessible (https://bugzilla.redhat.com/show_bug.cgi?id=1183977). Now, the domain doesn't get stuck in locked state, the operation is terminated as expected


Verified using rhev 3.5 vt13.9
rhevm-3.5.0-0.31.el6ev.noarch

Comment 11 errata-xmlrpc 2015-02-16 14:40:32 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.

https://rhn.redhat.com/errata/RHBA-2015-0226.html