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
[root@nomad-dev-0 ~]# nomad plugin status -verbose
Container Storage Interface
ID Provider Controllers Healthy/Expected Nodes Healthy/Expected
cinder-csi cinder.csi.openstack.org 3/3 3/3
Volume Status
[root@nomad-dev-0 ~]# nomad volume status
Container Storage Interface
ID Name Plugin ID Schedulable Access Mode
testvol test_volume cinder-csi true single-node-writer
Issue
When attempting to load the status of a specific volume after it has already been allocated to a job, the /v1/volume/csi/:volumeID endpoint fails leading to both the nomad volume status [volumeID] command and the UI to fail.
Output when trying to view the status of a Volume that has been allocated to a job already:
[root@nomad-dev-0 ~]# nomad volume status testvol
Error querying volume: Get "https://nomad-dev-0.eco.cpanel.net:4646/v1/volume/csi/testvol": EOF
I checked the logs and found the issue is the result of an invalid memory address/nil pointer dereference.
This doesn't happen when the volume is not actively allocated to a job.
[root@nomad-dev-0 ~]# nomad job stop metrics-server
==> Monitoring evaluation "b7751916"
Evaluation triggered by job "metrics-server"
Evaluation within deployment: "90826e0d"
Evaluation status changed: "pending" -> "complete"
==> Evaluation "b7751916" finished with status "complete"
[root@nomad-dev-0 ~]# nomad volume status testvol
ID = testvol
Name = test_volume
External ID = [openstack-external-id]
Plugin ID = cinder-csi
Provider = cinder.csi.openstack.org
Version = 1.2.0@latest
Schedulable = true
Controllers Healthy = 3
Controllers Expected = 3
Nodes Healthy = 3
Nodes Expected = 3
Access Mode = single-node-writer
Attachment Mode = block-device
Mount Options = <none>
Namespace = default
Allocations
No allocations placed
Reproduction steps
Deploy the Cinder CSI plugin (others may cause the behavior as well, haven't tested any though)
Register a Volume
Check the volumes status and see that it loads
Deploy a job that claims the volume
Check the volumes status again and note the errors.
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
For reporting security vulnerabilities please refer to the website.
If you have a question, prepend your issue with
[question]
or preferably use the nomad mailing list.If filing a bug please include the following:
Nomad version
Operating system and Environment details
Cinder CSI Plugin being used:
Volume Status
Issue
When attempting to load the status of a specific volume after it has already been allocated to a job, the
/v1/volume/csi/:volumeID
endpoint fails leading to both thenomad volume status [volumeID]
command and the UI to fail.Output when trying to view the status of a Volume that has been allocated to a job already:
I checked the logs and found the issue is the result of an invalid memory address/nil pointer dereference.
This doesn't happen when the volume is not actively allocated to a job.
Reproduction steps
Job file (if appropriate)
Volume Registration Configuration
Nomad Client logs (if appropriate)
Nothing was found related to this error in the Client logs
Nomad Server logs (if appropriate)
The text was updated successfully, but these errors were encountered: