+++ This bug was initially created as a clone of Bug #2145114 +++
Description of problem:
stderr from lvcreate is not included in the error we get from the LVM DBus job with the latest LVM 2.03.17.
Version-Release number of selected component (if applicable):
$ lvm version
LVM version: 2.03.17(2) (2022-11-10)
Library version: 1.02.187 (2022-11-10)
Steps to Reproduce:
Try to create an LV that is too big for the VG, The call fails as expected but, stderr is empty.
# busctl call com.redhat.lvmdbus1 /com/redhat/lvmdbus1/Vg/0 com.redhat.lvmdbus1.Vg LvCreate "sta(ott)ia{sv}" test $((10*1024**3)) 0 0 0
(oo) "/" "/com/redhat/lvmdbus1/Job/0"
# busctl get-property com.redhat.lvmdbus1 /com/redhat/lvmdbus1/Job/0 com.redhat.lvmdbus1.Job GetError
(is) -1 "(\'com.redhat.lvmdbus1.Vg\', \'Exit code 5, stderr = \')"
Expected results:
With older LVM, the stderr is part of the error.
# busctl get-property com.redhat.lvmdbus1 /com/redhat/lvmdbus1/Job/0 com.redhat.lvmdbus1.Job GetError
(is) -1 "(\'com.redhat.lvmdbus1.Vg\', \'Exit code 5, stderr = Volume group \"testVG\" has insufficient free space (510 extents): 2560 required.\\n\')"
--- Additional comment from Tony Asleson on 2022-11-28 14:51:03 UTC ---
According to @vtrefny stderr is present when running lvm command separately. Issue is with dbus daemon.
--- Additional comment from Tony Asleson on 2022-11-29 19:02:48 UTC ---
Correction posted upstream: https://sourceware.org/git/?p=lvm2.git;a=commit;h=e63b0c7262f50ab43fcde1c50b6d880acab68407
--- Additional comment from Vojtech Trefny on 2022-11-30 07:47:50 UTC ---
Thank you, I can confirm the fix works (8f60c494515ddccb20e4afb804edb6b9599e65c0 is also needed), libblockdev test suite (thanks to which I originally discovered the issue) is now passing. Can we get this to Fedora rawhide soon?
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (lvm2 bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:2544