-
Notifications
You must be signed in to change notification settings - Fork 138
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
improve by-id device name retrieval #1936
Comments
I am currently working on this issue. |
phillxnet
added a commit
to phillxnet/rockstor-core
that referenced
this issue
Jun 10, 2018
Some systemd/udev configs can push DEVLINKS from the top line of udevadm output: breaking an assumption made in get_dev_byid_name(). - Remove assumption that DEVLINKS line is first presented by udevadm. - Debug log if no DEVLINKS line was found. - Error log if device node not found. - Ensure determinism with multiple same length by-id names for the same device: ie via device links list sort prior to selection and return. - Add unit tests for get_dev_byid_name() to cover existing desired and above modified behaviour. - Refactor for readability / simplification. - Fix existing minor flake8 compliance in osi.py.
schakrava
added a commit
that referenced
this issue
Jun 19, 2018
…e_retrieval improve by-id device name retrieval. Fixes #1936
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Under certain systemd/udev configurations it was found that the current get_dev_byid_name() method was unable to retrieve an available /dev/disk/by-id name, failing over to the canonical temp sda type names. This was observed in a pre-release testing environment but could affect any similarly custom configured released Rockstor instances, but has not been seen or reported as such. It was also noted that in circumstances where 2 or more by-id names have identical lengths the same method was not deterministic; this is a universal issue but should be a rare occurrence.
The text was updated successfully, but these errors were encountered: