Bug 1244902
Summary: | [New] - Editing a host protocol from xml to json rpc does not work in rhsc. | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | RamaKasturi <knarra> |
Component: | rhsc | Assignee: | Sahina Bose <sabose> |
Status: | CLOSED ERRATA | QA Contact: | RHS-C QE <rhsc-qe-bugs> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | rhgs-3.1 | CC: | asriram, asrivast, bmohanra, dpati, knarra, nlevinki, pkliczew, rcyriac, rhs-bugs, sabose, vagarwal |
Target Milestone: | --- | Keywords: | Reopened, ZStream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | rhsc-3.1.0-65 | Doc Type: | Bug Fix |
Doc Text: |
Previously, editing a host protocol from xml-rpc to json-rpc and then activating the host caused the host to become non-operational due to connectivity issues. This issue is now fixed.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2015-10-05 09:23:01 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1216951 |
Description
RamaKasturi
2015-07-20 18:03:34 UTC
Kasturi, could you add the logs from engine and vdsm? Doc text is edited. Please sign off to be included in Known Issues. Looks good Closing as this bug was not reproducible. Please re-open with logs if you face the issue again Moving BZ to ASSIGNED for proper closure of bug, since report of issue occurrence and report of issue 'fix' span across different release builds Please verify on latest build Verified and works fine with build rhsc-3.1.1-0.65.el6.noarch Status of host shows up once the protocol is edited to JSON from xmlrpc. Marking this bug verified Slightly edited the doc text. 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-1848.html |