-
Notifications
You must be signed in to change notification settings - Fork 591
Testing/ceph tentacle #5894
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: devel
Are you sure you want to change the base?
Testing/ceph tentacle #5894
Conversation
Recent versions of Rook use Ceph-CSI Operator by default. There is no need to have Ceph-CSI deployed by Rook, as our CI deploys it from the PR that is being tested. Signed-off-by: Niels de Vos <ndevos@ibm.com>
Signed-off-by: Niels de Vos <ndevos@ibm.com>
ceph-volume in Tentacle (v20) uses udev data to detect some properties of the potential OSDs. Inside the minikube cluster (running with Podman), there is no udev. Mounting the host udev runtime data into the containers makes ceph-volume happy. Signed-off-by: Niels de Vos <ndevos@ibm.com>
When the CephFS e2e tests run on Ceph Tentacle (v20), they always fail
during
check data persist after recreating pod
With standard yaml deployment, the e2e tests succeed.
With Ceph Reef (v19) and Helm, the e2e tests succeed.
See-also: ceph#5772
Signed-off-by: Niels de Vos <ndevos@ibm.com>
Signed-off-by: Niels de Vos <ndevos@ibm.com>
With Ceph Tentacle creating a (the first?) NFS-export fails with:
```
Error EINVAL: Traceback (most recent call last):
File "/usr/share/ceph/mgr/mgr_module.py", line 2010, in _handle_command
return CLICommand.COMMANDS[cmd['prefix']].call(self, cmd, inbuf)
File "/usr/share/ceph/mgr/mgr_module.py", line 534, in call
return self.func(mgr, **kwargs)
File "/usr/share/ceph/mgr/object_format.py", line 592, in _format_response
robj = f(*args, **kwargs)
File "/usr/share/ceph/mgr/nfs/module.py", line 45, in
_cmd_nfs_export_create_cephfs
earmark_resolver = CephFSEarmarkResolver(self)
File "/usr/share/ceph/mgr/mgr_util.py", line 356, in __init__
self._cephfs_client = client or CephfsClient(mgr)
File "/usr/share/ceph/mgr/mgr_util.py", line 318, in __init__
self.connection_pool = CephfsConnectionPool(self.mgr)
File "/usr/share/ceph/mgr/mgr_util.py", line 223, in __init__
self.timer_task.start()
File "/usr/lib64/python3.9/threading.py", line 899, in start
_start_new_thread(self._bootstrap, ())
RuntimeError: can't start new thread
```
It seems this can only happen when the CLI is used, that means go-ceph
failed to create the export in the first place. It would be useful to
log the go-ceph failure, so that improving is possible.
Signed-off-by: Niels de Vos <ndevos@ibm.com>
Signed-off-by: Niels de Vos <ndevos@ibm.com>
Signed-off-by: Niels de Vos <ndevos@ibm.com>
This commit switches cephcsi base image to tentacle v20 Signed-off-by: Rakshith R <rar@redhat.com>
Signed-off-by: Rakshith R <rar@redhat.com>
|
/test ci/centos/mini-e2e/k8s-1.34 |
|
/test ci/centos/mini-e2e/k8s-1.34/cephfs |
|
/test ci/centos/mini-e2e/k8s-1.34/rbd |
|
/test ci/centos/mini-e2e/k8s-1.34/nfs |
Signed-off-by: Rakshith R <rar@redhat.com>
|
/test ci/centos/mini-e2e/k8s-1.34/rbd |
|
/test ci/centos/mini-e2e/k8s-1.34/nfs |
cephfs run passed 🎉 ! |
Signed-off-by: Rakshith R <rar@redhat.com>
|
/test ci/centos/mini-e2e/k8s-1.34/rbd |
|
Signed-off-by: Rakshith R <rar@redhat.com>
|
/test ci/centos/mini-e2e/k8s-1.34/nfs |
https://jenkins-ceph-csi.apps.ocp.cloud.ci.centos.org/job/mini-e2e_k8s-1.34-nfs/4/display/redirect Nfs passed too |
Describe what this PR does
Provide some context for the reviewer
Is there anything that requires special attention
Do you have any questions?
Is the change backward compatible?
Are there concerns around backward compatibility?
Provide any external context for the change, if any.
For example:
Related issues
Mention any github issues relevant to this PR. Adding below line
will help to auto close the issue once the PR is merged.
Fixes: #issue_number
Future concerns
List items that are not part of the PR and do not impact it's
functionality, but are work items that can be taken up subsequently.
Checklist:
guidelines in the developer
guide.
Request
notes
updated with breaking and/or notable changes for the next major release.
Show available bot commands
These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:
/retest ci/centos/<job-name>: retest the<job-name>after unrelatedfailure (please report the failure too!)