-
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
5.0.9-0 & 5.0.10-0 lsblk whitespace only values - not enough values to unpack #2853
Comments
Python console reproducer:Our failing line parse looks to be:
Working line example:Where-as if we do the same on a working line we have:
Reproducer lsblk output taken from McFaul's forum feedback using a VM instance of Rockstor with a drive passthrough. Initial suspicion is that this is VM only and relates to the following lsblk element provided by the hypervisor:
We now have a unit test reproducer for this issue as reported. |
Suggestion reinforcing suspicion re whitespace VENDOR as provided by hypervisor and we have:
I.e. previously failing line parse works as expected. We are dealing with an unsupported platform here, but I'll look for a bit at viable work-arounds if they do not overly complicate all other supported instances for the same of buggy hypervisor communications of drive VENDOR as indicated. |
…o unpack rockstor#2853 VM instance report had all whitespace VENDOR value returned by lsblk. Add re.sub() pre-processor to each lsblk line prior to main parsing. Includes - Remarked out (noisy) debug line to easy future investigations. - Additional unit-test reproducer to prove fix and guard against regression.
…-whitespace-only-values---not-enough-values-to-unpack 5.0.9-0 & 5.0.10-0 lsblk whitespace only values - not enough values to unpack #2853
Closing as: |
Thanks to forum member coffax for highlighting this issue, and McFaul for confirming. No lsblk serial (SERIAL="") fails to parse with the following error:
Blocking our prior fail-over too udev for serial retrieval. And given this is a low level failure, uncaught, we end up with no drive info.
Requirements
Forum reference: https://forum.rockstor.com/t/houston-weve-had-a-problem-not-enough-values-to-unpack-expected-2-got-1/9534
The text was updated successfully, but these errors were encountered: