Bug 1115466
Summary: | reconstructMaster() takes exactly 10 arguments (9 given) when using jsonrpc | ||
---|---|---|---|
Product: | [Retired] oVirt | Reporter: | Nir Soffer <nsoffer> |
Component: | vdsm-jsonrpc-java | Assignee: | Piotr Kliczewski <pkliczew> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Petr Beňas <pbenas> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.5 | CC: | amureini, bazulay, bugs, iheim, nsoffer, oourfali, pstehlik, smizrahi |
Target Milestone: | --- | ||
Target Release: | 3.5.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | infra | ||
Fixed In Version: | ovirt-3.5.0-beta1.1 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-10-17 12:41:18 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: | |||
Bug Depends On: | 1128761 | ||
Bug Blocks: | 1073943 |
Description
Nir Soffer
2014-07-02 12:20:15 UTC
Note: the schema is *incorrect* - the missing parameter is the hostId and not storagepoolID. See vdsm/API.py: def reconstructMaster(self, hostId, name, masterSdUUID, masterVersion, domainDict, lockRenewalIntervalSec, leaseTimeSec, ioOpTimeoutSec, leaseRetries): lockPolicy = None # Not used return self._irs.reconstructMaster( self._UUID, name, masterSdUUID, domainDict, masterVersion, lockPolicy, lockRenewalIntervalSec, leaseTimeSec, ioOpTimeoutSec, leaseRetries, hostId) The pool id is is self._UUID and is not needed in this verb. Can you please provide more detailed steps to reproduce? How can one start the reconstract flow? (In reply to Petr Beňas from comment #2) > How can one start the reconstract flow? 1. Create a DC with two or more storage domains. 2. Move the master storage domain to maintenance - this should force the master to be reconstructed on another domain. Verified in oVirt Engine Version: 3.5.0-0.0.master.20140821064931.gitb794d66.el6 with comment 3 steps oVirt 3.5 has been released and should include the fix for this issue. |