Deviation from expected behavior:
SVG cleanup job fails due to missing cephFS SubVolumeGroup env variable.
Expected behavior:
SVG cleanup job should not fail
How to reproduce it (minimal and precise):
Create rook ceph cluster.
Create SVG subvolume group but don't provide spec.Name
Add cleanup annotation to the subvolume group.
Delete the subvolume group resource.
Observe the cleanup job.
Jobs fails due to missing env variable because operator is only reading the subvolumeGroupName from spec.Name in the subvolumeGroupResource.
$ k logs cleanup-svg-9b7989c82f0b72ee4f9e1b92444f221b-qn99p -f
2024/05/17 10:53:30 maxprocs: Leaving GOMAXPROCS=8: CPU quota undefined
2024-05-17 10:53:30.650936 I | rookcmd: starting Rook v1.14.0-103.g3ddafdfe5 with arguments '/usr/local/bin/rook ceph clean CephFilesystemSubVolumeGroup'
2024-05-17 10:53:30.650954 I | rookcmd: flag values: --help=false, --log-level=DEBUG
2024-05-17 10:53:30.651594 C | rookcmd: cephFS SubVolumeGroup name is not available in the pod environment variables
File(s) to submit:
Cluster CR (custom resource), typically called cluster.yaml, if necessary
Logs to submit:
Operator's logs, if necessary
Crashing pod(s) logs, if necessary
To get logs, use kubectl -n <namespace> logs <pod name>
When pasting logs, always surround them with backticks or use the insert code button from the Github UI.
Read GitHub documentation if you need help.
Cluster Status to submit:
Output of kubectl commands, if necessary
To get the health of the cluster, use kubectl rook-ceph health
To get the status of the cluster, use kubectl rook-ceph ceph status
For more details, see the Rook kubectl Plugin
Environment:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Cloud provider or hardware configuration:
Rook version (use rook version inside of a Rook Pod):
Storage backend version (e.g. for ceph do ceph -v):
Kubernetes version (use kubectl version):
Kubernetes cluster type (e.g. Tectonic, GKE, OpenShift):
Storage backend status (e.g. for Ceph use ceph health in the Rook Ceph toolbox):
Is this a bug report or feature request?
Deviation from expected behavior: SVG cleanup job fails due to missing cephFS SubVolumeGroup env variable.
Expected behavior: SVG cleanup job should not fail
How to reproduce it (minimal and precise):
spec.NameJobs fails due to missing env variable because operator is only reading the subvolumeGroupName from
spec.Namein the subvolumeGroupResource.File(s) to submit:
cluster.yaml, if necessaryLogs to submit:
Crashing pod(s) logs, if necessary
To get logs, use
kubectl -n <namespace> logs <pod name>When pasting logs, always surround them with backticks or use theinsert codebutton from the Github UI. Read GitHub documentation if you need help.Cluster Status to submit:
Output of kubectl commands, if necessary
To get the health of the cluster, use
kubectl rook-ceph healthTo get the status of the cluster, usekubectl rook-ceph ceph statusFor more details, see the Rook kubectl PluginEnvironment:
uname -a):rook versioninside of a Rook Pod):ceph -v):kubectl version):ceph healthin the Rook Ceph toolbox):