Bug 1212762

Summary:

[HC] - gluster volume info api is broken with 3.6.2 client vs. 3.5.3 server

Product:

[Community] GlusterFS

Reporter:

Ala Hino <ahino>

Component:

core

Assignee:

Kaushal <kaushal>

Status:

CLOSED EOL

QA Contact:

Severity:

medium

Docs Contact:

Priority:

unspecified

Version:

3.6.2

CC:

ahino, amureini, bugs, kaushal, ylavi

Target Milestone:

---

Keywords:

Triaged

Target Release:

---

Hardware:

Unspecified

OS:

Linux

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2016-08-23 12:35:58 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:

Attachments:

Description	Flags
Client machine logs	none

Description Ala Hino 2015-04-17 09:52:06 UTC

Description of problem:

gluster volume info api is broken when running from remote client

How reproducible:

100%

Steps to Reproduce:

On a remote client, run following command, w/ or w/o --xml option: 
gluster volume info --xml


Actual results:

Partial info


Expected results:

All info

Additional info:

Running the command on gluster server works OK

Comment 1 Ala Hino 2015-04-17 09:52:54 UTC

Created attachment 1015508 [details]
Client machine logs

Comment 2 Allon Mureinik 2015-04-19 11:44:51 UTC

This bugs blocks oVirt's HC initiative (see bug 922744).
Can we get an ETA on the fix please?

Thanks!

Comment 3 Kaushal 2015-04-21 04:42:01 UTC

What versions of GlusterFS are you running on the remote client and on the gluster host?

Generally, the `gluster` command is compatible with a glusterd of the same version. It might work with mixed versions, but that is something we don't yet test and try to keep compatibility.

Comment 4 Ala Hino 2015-04-21 05:39:47 UTC

Good input.

There was an incompatibility between gluster remote client and gluster host.
When I tested the api, remote client version was 3.6.2 and host version was 3.5.3.

After upgrading host to version 3.7dev, the api is working as expected. Remote client wasn't changed.

Comment 5 Allon Mureinik 2015-04-21 08:54:30 UTC

Reducing severity based on the last comment.
Thanks Kaushal!

Comment 6 Kaushal 2015-04-22 09:18:53 UTC

Generally, older GlusterFS cli versions should work without any problems with newer versions of GlusterD. Newer versions of CLI will most often break with older versions of GlusterD.

The information passed from GlusterD to CLI generally increases in an additive manner between versions. So newer CLI will be expecting more information to be returned from GlusterD, but as an older GlusterD cannot give the information, CLI would fail. An older CLI would be expecting lesser information than a new GlusterD would provide, so an older CLI will most likely work with a newer GlusterD. There could be some failures here as well, but probably due to actual bugs that would have been fixed in the newer versions.

Comment 7 Kaushal 2016-08-23 12:35:58 UTC

This bug is being closed as GlusterFS-3.6 is nearing its End-Of-Life and only important security bugs will be fixed. If you still face this bug with the newer GlusterFS versions, please open a new bug.