You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to upgrade my ceph-iscsi 3.4 environment's underlying ceph/rbd packages to use the latest nautilus release. Going from 14.2.6 to 14.2.11
If I recall correctly in testing I just bounced the tcmu-runner daemon and this would cause "ceph versions" to report the new versions for tcmu-runner. However, now that I have some production workload I wanted to verify this was the proper way to do things?
Googling around I found this: https://bugzilla.redhat.com/show_bug.cgi?id=1568581 which says "Normally, the user should not be starting/stopping tcmu-runner manually. Components like rtslib and rbd-target-gw/ceph-iscsi-config and systemd will handle this."
So my question is, during such upgrades, what is the best practice way for an operator to cause tcmu-runner to begin using the new version of ceph.
Thanks in advance.
The text was updated successfully, but these errors were encountered:
That BZ was referring to a bug in pre-RHEL 7.6 kernels where IO could get permanently stuck in the kernel IO ring requiring a reboot of the box to recover.
Correct, shouldn't be an issue if the kernel version isn't an issue. The ceph-ansible rolling upgrade script will stop the iSCSI services on a node, upgrade, and then restart [1]
I would like to upgrade my ceph-iscsi 3.4 environment's underlying ceph/rbd packages to use the latest nautilus release. Going from 14.2.6 to 14.2.11
If I recall correctly in testing I just bounced the tcmu-runner daemon and this would cause "ceph versions" to report the new versions for tcmu-runner. However, now that I have some production workload I wanted to verify this was the proper way to do things?
Googling around I found this: https://bugzilla.redhat.com/show_bug.cgi?id=1568581 which says "Normally, the user should not be starting/stopping tcmu-runner manually. Components like rtslib and rbd-target-gw/ceph-iscsi-config and systemd will handle this."
So my question is, during such upgrades, what is the best practice way for an operator to cause tcmu-runner to begin using the new version of ceph.
Thanks in advance.
The text was updated successfully, but these errors were encountered: