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
storage: tests_luks.yml partition case failed with nvme disk #141
Comments
yizhanglinux
changed the title
storage: tests_luks.yml failed with nvme disk
storage: tests_luks.yml partition case failed with nvme disk
Aug 4, 2020
dwlehman
added a commit
to dwlehman/storage
that referenced
this issue
Aug 4, 2020
So it's not related to luks, bellow playbook also can reproduce this issue.
|
dwlehman
added a commit
to dwlehman/storage
that referenced
this issue
Aug 20, 2020
BlivetVolume._get_device_id is only used to look up pre-existing volumes, so we don't have to try too hard to guess it by name. We can just see if the disk has a single partition and, if so, return the name of that partition. Fixes: linux-system-roles#141
dwlehman
added a commit
to dwlehman/storage
that referenced
this issue
Aug 20, 2020
BlivetVolume._get_device_id is only used to look up pre-existing volumes, so we don't have to try too hard to guess it by name. We can just see if the disk has a single partition and, if so, return the name of that partition. Fixes: linux-system-roles#141
dwlehman
added a commit
to dwlehman/storage
that referenced
this issue
Mar 12, 2021
BlivetVolume._get_device_id is only used to look up pre-existing volumes, so we don't have to try too hard to guess it by name. We can just see if the disk has a single partition and, if so, return the name of that partition. Fixes: linux-system-roles#141
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue can be reproduced with NVMe disk on RHEL7/8
playbook
Detailed Log
# ansible-playbook -i inventory tests/tests_luks.yml -vvv
/tmp/blivet.log
# cat /tmp/blivet.log | tail -300
The text was updated successfully, but these errors were encountered: