Skip to content

Fix block device conversion #253

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

Merged
merged 2 commits into from
Jan 9, 2019

Conversation

lukeseawalker
Copy link
Contributor

The block device returned by the parallelcluster-ebsnvme-id script must
be in format suitable for udev rules

E.g.

  • without -u flag
    parallelcluster-ebsnvme-id -b /dev/nvme0n1 return sda1
    parallelcluster-ebsnvme-id -b /dev/nvme1n1 return /dev/sdb

  • with -u flag
    parallelcluster-ebsnvme-id -u -b /dev/nvme0n1 return sda1
    parallelcluster-ebsnvme-id -u -b /dev/nvme1n1 return sdb

This fix aws/aws-parallelcluster#823

Signed-off-by: Luca Carrogu [email protected]

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

The block device returned by the parallelcluster-ebsnvme-id script must
be in format suitable for udev rules

E.g.
- without -u flag
parallelcluster-ebsnvme-id -b /dev/nvme0n1 return sda1
parallelcluster-ebsnvme-id -b /dev/nvme1n1 return /dev/sdb

- with -u flag
parallelcluster-ebsnvme-id -u -b /dev/nvme0n1 return sda1
parallelcluster-ebsnvme-id -u -b /dev/nvme1n1 return sdb

This fix aws/aws-parallelcluster#823

Signed-off-by: Luca Carrogu <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Parallelcluster 2.1.1 with raid 0 config on Cent OS 7 fails in create cluster
2 participants