Bug 2230254

Summary:	[cee/sd][RADOS] cephx server client.crash.XXX: handle_request failed to decode CephXAuthenticate: End of buffer
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Tridibesh Chakraborty <trchakra>
Component:	RADOS	Assignee:	Radoslaw Zarzynski <rzarzyns>
Status:	NEW ---	QA Contact:	Pawan <pdhiran>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	5.3	CC:	bhubbard, ceph-eng-bugs, cephqe-warriors, nojha, rzarzyns, vumrao
Target Milestone:	---	Flags:	trchakra: needinfo? (rzarzyns) trchakra: needinfo? (rzarzyns)
Target Release:	7.1
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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:

Description Tridibesh Chakraborty 2023-08-09 07:18:22 UTC

Description of problem:

Customer recently upgraded to RHCS 5.3z3 and after that he started noticing error messages related to crash daemon where it is unable to connect to the cluster and logging `monclient(hunting): handle_auth_bad_method server allowed_methods [2] but i only support [2,1]` messages. 

Version-Release number of selected component (if applicable):

RHCS 5.3z3 : 16.2.10-172.el8cp

How reproducible:

I am unable to reproduce it on my lab cluster. This issue is visible on customer environment only. 

Steps to Reproduce:

Nil

Actual results:

Getting below messages in syslog on monitor node:

~~~
Aug 02 06:41:01 lxrgwp05arch.ux.dvint.de ceph-c0b13019-e62f-4fcb-80c4-5e9f69b94248-crash-lxrgwp05arch[15879]: WARNING:ceph-crash:post /var/lib/ceph/crash/2023-08-01T22:10:45.831791Z_0aeed091-9f6f-4c81-a616-bf7df2c080aa as client.crash.lxrgwp05arch failed: 2023-08-02T04:41:01.039+0000 7f432affd700 -1 monclient(hunting): handle_auth_bad_method server allowed_methods [2] but i only support [2,1]
Aug 02 06:41:00 lxrgwp05arch.ux.dvint.de ceph-c0b13019-e62f-4fcb-80c4-5e9f69b94248-crash-lxrgwp05arch[15879]:
Aug 02 06:41:00 lxrgwp05arch.ux.dvint.de ceph-c0b13019-e62f-4fcb-80c4-5e9f69b94248-crash-lxrgwp05arch[15879]: [errno 13] RADOS permission denied (error connecting to the cluster)
Aug 02 06:41:00 lxrgwp05arch.ux.dvint.de ceph-c0b13019-e62f-4fcb-80c4-5e9f69b94248-crash-lxrgwp05arch[15879]: 2023-08-02T04:41:00.903+0000 7f63a8b41700 -1 monclient(hunting): handle_auth_bad_method server allowed_methods [2] but i only support [2,1]
Aug 02 06:41:00 lxrgwp05arch.ux.dvint.de ceph-c0b13019-e62f-4fcb-80c4-5e9f69b94248-crash-lxrgwp05arch[15879]: 2023-08-02T04:41:00.902+0000 7f639b7fe700 -1 monclient(hunting): handle_auth_bad_method server allowed_methods [2] but i only support [2,1]
~~~

Expected results:

The crash daemons should be able to connect to the cluster. 

Additional info:

By seeing the error message, initially I thought that the version of the crash daemon might be older or it is missing the keyring. But when I verified, I can see it is of same version as cluster and also have the valid keyring under /var/lib/ceph/<fsid>/crash.<hostname> directory (filename: keyring). Also the permission is set to 600 and owner is Ceph.