Skip to content
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

Unable to interpolate NOMAD_ALLOC_INDEX in group volume stanza #8540

Closed
ryanmickler opened this issue Jul 27, 2020 · 2 comments
Closed

Unable to interpolate NOMAD_ALLOC_INDEX in group volume stanza #8540

ryanmickler opened this issue Jul 27, 2020 · 2 comments

Comments

@ryanmickler
Copy link
Contributor

ryanmickler commented Jul 27, 2020

Nomad version

11.3

Operating system and Environment details

ubuntu bionic

Issue

In order to deploy a (scalable) cluster of tasks, each with their own persistent volume, I need to be able to interpolate the group allocation index in the volume stanza at the group level. Each allocation group needs to have its own persistent volume.

In the Nomad UI, i see that the following error, indicating that no interpolation has happened.
Constraint missing CSI Volume csi-test-${NOMAD_ALLOC_INDEX} filtered 4 nodes

Job file

...

    group "group" {

        volume "group_csi_volume" {
            type = "csi"
            read_only = false
            source = "csi-test-${NOMAD_ALLOC_INDEX}"
        }

        ...
@tgross
Copy link
Member

tgross commented Jul 27, 2020

Hi @ryanmickler! Thanks for opening this issue. It looks like this is a duplicate of #7877, so I'm going to close it. But it's definitely on our radar!

@github-actions
Copy link

github-actions bot commented Nov 4, 2022

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants