+++ This bug was initially created as a clone of Bug #2164044 +++

+++ 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.

1. 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"

1. 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.

1. 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?

— Additional comment from Corey Marthaler on 2023-01-25 16:15:31 UTC —

Adding QA ack for 9.2.

This bug will be marked verified based on the results mentioned above, once initial 9.2 regression testing has been completed.

— Additional comment from RHEL Program Management on 2023-02-01 07:28:18 UTC —

DevMissed

The Current Deadline for this BZ has passed. Please discuss with your PO & QE Contact and revise the Current Deadline in one of the following ways:

1. Update the Devel Target Milestone (DTM) to when you think the work will be ready for verification.
2. Set a Custom Deadline Type and Date to when you think the work will be ready for verification.
3. Update the Internal Target Milestone (ITM) according to QE guidance. In the absence of 1 and 2 above, the Current Deadline is automatically set to 6 days before the ITM date.

Note that BZs that miss their due date by more than 2 weeks will automatically lose their ITM and thus their release+.
Resetting ITM will cause release+ to be restored.

More details about deadline management are available at https://one.redhat.com/rhel-developer-guide/#proc_using-deadlines-to-prioritize-work_assembly_development

— Additional comment from Corey Marthaler on 2023-02-07 23:15:56 UTC —

Marking Verified:Tested with the latest rpms.

kernel-5.14.0-231.el9 BUILT: Mon Jan 9 08:32:41 PM CET 2023
lvm2-2.03.17-5.el9 BUILT: Thu Jan 26 11:17:14 PM CET 2023
lvm2-libs-2.03.17-5.el9 BUILT: Thu Jan 26 11:17:14 PM CET 2023

— Additional comment from errata-xmlrpc on 2023-02-09 18:05:56 UTC —

This bug has been added to advisory RHBA-2022:106892 by Marian Csontos (mcsontos@redhat.com)

— Additional comment from errata-xmlrpc on 2023-02-09 18:05:57 UTC —

Bug report changed to ON_QA status by Errata System.
A QE request has been submitted for advisory RHBA-2022:106892-02
https://errata.devel.redhat.com/advisory/106892

— Additional comment from errata-xmlrpc on 2023-05-09 00:35:37 UTC —

Bug report changed to RELEASE_PENDING status by Errata System.
Advisory RHBA-2022:106892-02 has been changed to PUSH_READY status.
https://errata.devel.redhat.com/advisory/106892

— Additional comment from errata-xmlrpc on 2023-05-09 08:23:51 UTC —

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