-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
GCE CSI driver not claiming volumes successfully registered in Nomad #7901
Comments
referencing the ID from
excerpt from job file:
Closing issue. |
the above correction placed the allocation but is still not acting as expected, and logs are showing that the volume can still not be found: client logs:
jobsec:
chaning to the volume ID under volume_mount give error running job |
The jobspec has the following: But that's not the ID, it's an ID prefix. You can use the prefix of the ID in commands like |
That fixed it, thanks @tgross can succesfully attach volume, write some data, purge job, start job and data has persisted, which i have been trying to figure out with this driver since #7734 . Thanks for including that fix from #7734 in the 0.11.1 release and for pointing out my mistake here, much appreciated. |
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. |
###Nomad version
Nomad v0.11.1 (b434570)
Issue
Created persistent disk and successfully registered the volume. When running a Nomad job that should claim the volume, hitting following error:
i'm using this persistent disk:
volume registration file:
The volume is showing as registered:
Job spec:
###Job status:
The text was updated successfully, but these errors were encountered: