http://bugzilla.suse.com/show_bug.cgi?id=1148809
http://bugzilla.suse.com/show_bug.cgi?id=1148809#c10
--- Comment #10 from Adam Spiers
(In reply to Adam Spiers from comment #7)
With your test package grub2-editenv runs fine with exit code 0 (although the fd leakage is still there).
The fd leakage should be harmless,
Let's call it "*mostly* harmless" ;-) Any unnecessary pollution of log files makes true errors harder to spot, therefore it is still harmful to a small extent.
however I'll see if I could come up with a fix as well.
That would be great, thanks!
However as expected, the original problem with libstorage-ng as stated in https://github.com/openSUSE/libstorage-ng/issues/664 remains.
I am not clear on this part "original problem". Was it saying grub2-editenv still fail in yast bootloader ?
No, the original problem is that libstorage-ng can't correctly recognise cached LVs since the first byte of their lv_attr is 'C', so it gives them LvType::UNKNOWN and then fails to detect the filesystem. This is explained in detail in the original report at the top of https://github.com/openSUSE/libstorage-ng/issues/664 I have proposed a simple fix in my latest comment there. -- You are receiving this mail because: You are on the CC list for the bug.