health-checker should get started during NodeGetVolumeStats call if not running yet
#4219
Assignees
Labels
component/cephfs
Issues related to CephFS
Comments
nixpanic
added a commit
to nixpanic/ceph-csi
that referenced
this issue
Nov 2, 2023
The HealthChecker is configured to use the Staging path pf the volume, with a `.csi/` subdirectory. In the future this directory could be a directory that is not under the Published directory. Fixes: ceph#4219 Signed-off-by: Niels de Vos <[email protected]>
nixpanic
added a commit
to nixpanic/ceph-csi
that referenced
this issue
Nov 3, 2023
The HealthChecker is configured to use the Staging path pf the volume, with a `.csi/` subdirectory. In the future this directory could be a directory that is not under the Published directory. Fixes: ceph#4219 Signed-off-by: Niels de Vos <[email protected]>
nixpanic
added a commit
to nixpanic/ceph-csi
that referenced
this issue
Nov 3, 2023
The HealthChecker is configured to use the Staging path pf the volume, with a `.csi/` subdirectory. In the future this directory could be a directory that is not under the Published directory. Fixes: ceph#4219 Signed-off-by: Niels de Vos <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As mentioned in #4200, the health-checker may not be running when
NodeGetVolumeStatsgets called. It is possible that the CephFS-nodeplugin was restarted (updated) while a volume was already mounted and used by an application.A difficulty here is that the
NodeGetVolumeStatscall only passes the publish-path for the volume, and the health-checker is using the staging-path (to prevent running multiple checkers for the same volume).The text was updated successfully, but these errors were encountered: