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

Should fix dependency on volume order #327

Closed
sjpb opened this issue Nov 24, 2023 · 0 comments · Fixed by #341
Closed

Should fix dependency on volume order #327

sjpb opened this issue Nov 24, 2023 · 0 comments · Fixed by #341

Comments

@sjpb
Copy link
Collaborator

sjpb commented Nov 24, 2023

Currently, the slurm app TF (and caas) relies (here, here) on the fact that block devices are attached in the order they are defined; so if labels are applied in that order they end up on the right devices/filesystems. This works for RL8.6 and RL8.8 genericcloud images, actually I don't think it did for RL8.7 and it doesn't for RL9.2. For that, labels are getting applied to the expected devices, it's just that the device ordering isn't consistent with the definition order.

There is a fix at 93c70c0, which would also mean we could get rid of caas's inspection of image properties to define the correct volume path.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant