Bug 1209457

Summary:	[New] - When host is added to cluster using xml rpc it says "gluster command failed on server"
Product:	[Retired] oVirt	Reporter:	RamaKasturi <knarra>
Component:	ovirt-engine-webadmin	Assignee:	Sahina Bose <sabose>
Status:	CLOSED WORKSFORME	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.6	CC:	bugs, dnarayan, dpati, ecohen, gklein, lsurette, mgoldboi, pkliczew, rbalakri, yeylon
Target Milestone:	---
Target Release:	3.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	gluster
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-05-13 06:36:20 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Gluster	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1187461

Description RamaKasturi 2015-04-07 12:03:46 UTC

Description of problem:
When a node is added to 3.6 cluster using xml rpc in the general sub tab of Action Items section it always says "Gluster command failed on server"

Version-Release number of selected component (if applicable):
ovirt-engine-webadmin-portal-3.6.0-0.0.master.20150406175153.gite240701.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Add a rhel7 host to the cluster using xml rpc.
2. Now click on the general subtab of hosts.
3. 

Actual results:
In the action items section it displays "gluster command failed on server"

Expected results:
User should not be seeing this in the general sub tab of host.

Additional info:

Comment 1 RamaKasturi 2015-04-07 12:10:03 UTC

please find engine and vdsm logs in the link below.

http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/rhsc/1209457/

Comment 2 Sahina Bose 2015-05-04 12:48:45 UTC

From the vdsm logs on my setup:
Thread-27::ERROR::2015-05-04 18:07:41,251::BindingXMLRPC::261::BindingXMLRPC.RequestHandler::(send_error) Bad request version ('encodin
g="UTF-8"?><methodCall><methodName>glusterHostsList</methodName><params/></methodCall>')
Thread-28::ERROR::2015-05-04 18:07:41,259::BindingXMLRPC::261::BindingXMLRPC.RequestHandler::(send_error) Bad request syntax ('P')

vdsm version:
vdsm-4.17.0-614.gitd2905ba.fc20.x86_64


Piotr, is this a known issue?

Comment 3 Piotr Kliczewski 2015-05-04 13:40:12 UTC

I am not aware of this issue. Please provide logs and I will take a look.

Comment 4 Sahina Bose 2015-05-07 10:50:15 UTC

Piotr,

I ran into Bug 1219429 while trying to reproduce issue with latest master.

Are you able to access the logs mentioned in comment 1?

Comment 5 Piotr Kliczewski 2015-05-07 12:22:51 UTC

In the log I can see:

Thread-29::ERROR::2015-04-07 17:46:28,099::BindingXMLRPC::261::BindingXMLRPC.RequestHandler::(send_error) Unsupported method ('OST')
Thread-29::ERROR::2015-04-07 17:46:28,101::BindingXMLRPC::261::BindingXMLRPC.RequestHandler::(send_error) Bad request version ('encoding="UTF-8"?><methodCall><methodName>glusterHostsList</methodName><params/></methodCall>')

The code which raise this error looks as following:

            mname = 'do_' + self.command
            if not hasattr(self, mname):
                self.send_error(501, "Unsupported method (%r)" % self.command)

How do you build your request? Why there is 'OST'?

Comment 6 Sahina Bose 2015-05-07 16:22:02 UTC

I see the same errors with other methods too...
Thread-22::ERROR::2015-04-07 16:48:04,796::BindingXMLRPC::261::BindingXMLRPC.RequestHandler::(send_error) Unsupported method ('OST')
Thread-22::ERROR::2015-04-07 16:48:04,798::BindingXMLRPC::261::BindingXMLRPC.RequestHandler::(send_error) Bad request version ('encoding="UTF-8"?><methodCall><methodName>getVdsHardwareInfo</methodName><params/></methodCall>')

But the same method glusterHostsList returns with result too :
Thread-13::DEBUG::2015-04-07 16:53:09,860::BindingXMLRPC::1159::vds::(wrapper) client [10.70.37.115]::call hostsList with () {}
Thread-13::DEBUG::2015-04-07 16:53:10,085::BindingXMLRPC::1166::vds::(wrapper) return hostsList with {'status': {'message': 'Done', 'code': 0}, 'hosts': [{'status': 'CONNECTED', 'hostname': '10.70.37.162/23', 'uuid': '83f7efc4-5fbd-46f6-8c46-0150f5af5f5d'}, {'status': 'CONNECTED', 'hostname': '10.70.36.1', 'uuid': '53ff9082-c862-4fc6-ac81-efebca2cfe90'}]}

Comment 7 Sahina Bose 2015-05-12 13:53:02 UTC

Could not reproduce with latest vdsm master - vdsm-4.17.0-783.git79781a1.fc21.x86_64

Logs - 
Thread-13::DEBUG::2015-05-12 19:05:12,618::BindingXMLRPC::1157::vds::(wrapper) client [10.3.226.170]::call hostsList with () {}
Thread-13::DEBUG::2015-05-12 19:05:12,778::BindingXMLRPC::1164::vds::(wrapper) return hostsList with {'status': {'message': 'Done', 'code': 0}, 'hosts': [{'status': 'CONNECTED', 'hostname': '10.70.43.181/22', 'uuid': '5dbb4b15-bc27-4c3f-a0d5-7aa9b8dfc05a'}]}


The gluster prefix seems to be removed from verbs. Was this intentional?

Comment 8 Piotr Kliczewski 2015-05-12 14:48:50 UTC

I am not sure where was the prefix removed but as I understand we should keep it.

Comment 9 Darshan 2015-05-13 06:07:47 UTC

The gluster prefix is not removed from the verbs and even logging has always been this way.

Comment 10 Sahina Bose 2015-05-13 06:36:20 UTC

Thanks for confirming Darshan.

Since I could not reproduce the issue with laster master of engine and vdsm, closing this.

Please reopen if you face the issue after upgrading your nodes.