Bug #62246: qa/cephfs: test_mount_mon_and_osd_caps_present_mds_caps_absent fails - CephFS - Ceph

Actions

Copy link

Bug #62246

open

qa/cephfs: test_mount_mon_and_osd_caps_present_mds_caps_absent fails

Added by Rishabh Dave 9 months ago. Updated 20 days ago.

Status:

Pending Backport

Priority:

Normal

Assignee:

Rishabh Dave

Category:

Target version:

% Done:

Source:

Tags:

backport_processed

Backport:

quincy,reef

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Component(FS):

Labels (FS):

Pull request ID:

41779

Crash signature (v1):

Crash signature (v2):

Description

Test method test_mount_mon_and_osd_caps_present_mds_caps_absent (in test_multifs_auth.TestClientsWithoutAuth) fails. Following is the traceback printed when it fails with vstart_runner.py -

2023-07-31 19:28:20,634.634 INFO:__main__:======================================================================
2023-07-31 19:28:20,634.634 INFO:__main__:ERROR: test_mount_mon_and_osd_caps_present_mds_caps_absent (tasks.cephfs.test_multifs_auth.TestClientsWithoutAuth.test_mount_mon_and_osd_caps_present_mds_caps_absent)
2023-07-31 19:28:20,634.634 INFO:__main__:----------------------------------------------------------------------
2023-07-31 19:28:20,634.634 INFO:__main__:Traceback (most recent call last):
2023-07-31 19:28:20,634.634 INFO:__main__:  File "/home/rishabh/repos/ceph/fs-authorize/qa/tasks/cephfs/test_multifs_auth.py", line 303, in test_mount_mon_and_osd_caps_present_mds_caps_absent
2023-07-31 19:28:20,634.634 INFO:__main__:    keyring_path = self.mount_a.client_remote.mktemp(data=keyring)
2023-07-31 19:28:20,634.634 INFO:__main__:                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2023-07-31 19:28:20,634.634 INFO:__main__:  File "/home/rishabh/repos/teuthology/venv-teuth/lib/python3.11/site-packages/teuthology/orchestra/remote.py", line 80, in mktemp
2023-07-31 19:28:20,634.634 INFO:__main__:    self.write_file(path=path, data=data)
2023-07-31 19:28:20,634.634 INFO:__main__:  File "/home/rishabh/repos/teuthology/venv-teuth/lib/python3.11/site-packages/teuthology/orchestra/remote.py", line 295, in write_file
2023-07-31 19:28:20,634.634 INFO:__main__:    self.run(args=args, stdin=data, quiet=True)
2023-07-31 19:28:20,634.634 INFO:__main__:  File "/home/rishabh/repos/ceph/fs-authorize/build/../qa/tasks/vstart_runner.py", line 417, in run
2023-07-31 19:28:20,634.634 INFO:__main__:    return self._do_run(**kwargs)
2023-07-31 19:28:20,634.634 INFO:__main__:           ^^^^^^^^^^^^^^^^^^^^^^
2023-07-31 19:28:20,634.634 INFO:__main__:  File "/home/rishabh/repos/ceph/fs-authorize/build/../qa/tasks/vstart_runner.py", line 448, in _do_run
2023-07-31 19:28:20,634.634 INFO:__main__:    subproc.stdin.write(stdin.getvalue())
2023-07-31 19:28:20,634.634 INFO:__main__:                        ^^^^^^^^^^^^^^
2023-07-31 19:28:20,634.634 INFO:__main__:AttributeError: 'LocalRemoteProcess' object has no attribute 'getvalue'

The root cause for this failure is this line in the helper method create_client() (which is located in qa.tasks.cephfs.cephfs_test_case.CephFSTestCase) - return self.run_ceph_cmd(f'auth get {self.client_name}'). The class that represents the process launched for running this command is returned by this line. This is incorrect since stdout of the command being run should be returned (which will contain the keyring of the client).

Related issues 3 (2 open — 1 closed)

Actions

Copy link

Updated by Rishabh Dave 9 months ago

This failure might be same as the one reported here - https://tracker.ceph.com/issues/62188. If the cause of both the failures are same, the difference in this issue's manifestation, is due to usage of different tracker tickets. For failure on ticket #62188, teuthology was used. And for the failure/traceback reported here, vstart_runner.py was used to run tests.

Actions

Copy link

Updated by Venky Shankar 9 months ago

Related to Bug #62188: AttributeError: 'RemoteProcess' object has no attribute 'read' added

Actions

Copy link

Updated by Venky Shankar 9 months ago

Rishabh Dave wrote:

This failure might be same as the one reported here - https://tracker.ceph.com/issues/62188. If the cause of both the failures are same, the difference in this issue's manifestation, is due to usage of different tracker tickets. For failure on ticket #62188, teuthology was used. And for the failure/traceback reported here, vstart_runner.py was used to run tests.

The status says "Fix Under Review", but has no link to the PR and I cannot find one.

Actions

Copy link