This repository has been archived by the owner on Oct 16, 2020. It is now read-only.
coreos-install fails on ZFS zvol depending on specified path #1599
Comments
nilsmeyer
added a commit
to nilsmeyer/init
that referenced
this issue
Oct 6, 2016
Resolving the symlink before using the Device Variable fixes issues with lsblk and blkid. Symlinks may be problematic when using ZFS and using a path like /dev/zvol/poolname/volname. Fixes coreos/bugs#1599 for me.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue Report
Bug
CoreOS Version
1122.2.0, master branch of coreos/init
Environment
Bare-metal Xeon E5 v4 system, Linux on Ubuntu 16.10, Linux 4.8.0, ZFS 0.6.5.8.
Expected Behavior
Successful install of CoreOS on the specified device.
Actual Behavior
Error message:
Error: return code 2 from ROOT_DEV=$(blkid -t "LABEL=ROOT" -o device "${DEVICE}"*)Reproduction Steps
Steps as on my system:
Other Information
It seems this is caused by the Device being a symlink, likely regardless of what the underlying device actually is. It works when resolving the symlink beforehand.
The text was updated successfully, but these errors were encountered: