-
Notifications
You must be signed in to change notification settings - Fork 590
ci: use Rook 1.18.4 and Ceph Tentacle #5672
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?
Conversation
|
/test ci/centos/mini-e2e/k8s-1.34 |
The devel branch will use a newer version of Rook and Ceph in the near future. That requires the images to be mirrored in the CI registry. See-also: ceph#5672 Signed-off-by: Niels de Vos <ndevos@ibm.com>
|
/test ci/centos/mini-e2e/k8s-1.34 |
|
/test ci/centos/mini-e2e/k8s-1.34 |
1 similar comment
|
/test ci/centos/mini-e2e/k8s-1.34 |
The devel branch will use a newer version of Rook and Ceph in the near future. That requires the images to be mirrored in the CI registry. See-also: #5672 Signed-off-by: Niels de Vos <ndevos@ibm.com>
c2dabc9 to
03040f1
Compare
|
/test ci/centos/mini-e2e/k8s-1.34 |
|
/test ci/centos/mini-e2e/k8s-1.33 |
03040f1 to
870215d
Compare
|
/test ci/centos/mini-e2e/k8s-1.34 |
870215d to
025e47a
Compare
|
/test ci/centos/mini-e2e/k8s-1.34 |
025e47a to
a40f06c
Compare
|
/test ci/centos/mini-e2e/k8s-1.34 |
a40f06c to
9b9119c
Compare
|
/test ci/centos/mini-e2e/k8s-1.34 |
1 similar comment
|
/test ci/centos/mini-e2e/k8s-1.34 |
960e97e to
4b7516f
Compare
|
/test ci/centos/mini-e2e/k8s-1.34 |
4b7516f to
48a4306
Compare
|
/test ci/centos/mini-e2e/k8s-1.34 |
1 similar comment
|
/test ci/centos/mini-e2e/k8s-1.34 |
b919ccd to
96abede
Compare
|
/test ci/centos/mini-e2e-operator/k8s-1.34 |
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>
2ae4c4f to
8a40298
Compare
|
/test ci/centos/mini-e2e-operator/k8s-1.34 |
|
/test ci/centos/mini-e2e-helm/k8s-1.34 |
|
/test ci/centos/mini-e2e/k8s-1.34 |
|
/test ci/centos/mini-e2e-operator/k8s-1.34/nfs |
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>
8a40298 to
0c82877
Compare
|
/test ci/centos/mini-e2e-operator/k8s-1.34 |
Signed-off-by: Niels de Vos <ndevos@ibm.com>
0c82877 to
2855fcd
Compare
|
/test ci/centos/mini-e2e-operator/k8s-1.34 |
|
ci/centos/mini-e2e-operator/k8s-1.34 didn't really fail, it timed out after 2 hours of e2e |
The other two (Helm and simple yaml) deployments already have a timeout of 150 minutes. Just the operator tests time-out at the moment. See-also: ceph#5672 Signed-off-by: Niels de Vos <ndevos@ibm.com>
The other two (Helm and simple yaml) deployments already have a timeout of 150 minutes. Just the operator tests time-out at the moment. See-also: #5672 Signed-off-by: Niels de Vos <ndevos@ibm.com>
|
/test ci/centos/mini-e2e-operator/k8s-1.34 |
1 similar comment
|
/test ci/centos/mini-e2e-operator/k8s-1.34 |
Signed-off-by: Niels de Vos <ndevos@ibm.com>
2d17f62 to
703779e
Compare
|
/test ci/centos/mini-e2e-operator/k8s-1.34 |
|
/test ci/centos/mini-e2e-operator/k8s-1.34/rbd |
|
/test ci/centos/mini-e2e-operator/k8s-1.34/cephfs |
|
/test ci/centos/mini-e2e-operator/k8s-1.34/nfs |
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.
Rook v1.18.4 works well with Ceph Squid (v19). But for NVMe-oF testing we need a Ceph Tentacle (v20) cluster.
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!)