Many test scenarios that check stderr to see if LVM properly identified issues are now failing because those warnings are now being reported to stdout instead. Is this an  expected change and if so was this mentioned in a feature request for rhel9.4?

kernel-5.14.0-362.8.1.el9_3    BUILT: Tue Oct  3 02:39:10 PM CEST 2023
lvm2-2.03.23-1.el9    BUILT: Tue Nov 28 02:15:42 PM CET 2023
lvm2-libs-2.03.23-1.el9    BUILT: Tue Nov 28 02:15:42 PM CET 2023


Below is a subset of all the scenarios that are not failing.


# RHEL9.3  (Warnings reported to stderr)

SCENARIO - enabling_devicesfile_w_existing_vgs_present:  Create
initial PV with devicesfile newly turned ON, with VGs already in
existence prior to enablement
vgcreate    devfile_VG /dev/sdb /dev/sdc /dev/sdd /dev/sde /dev/sdf
 Volume group "devfile_VG" successfully created with system ID
virt-494.cluster-qe.lab.eng.brq.redhat.com

Enabling devicesfile on virt-494.cluster-qe.lab.eng.brq.redhat.com
Setting use_devicesfile to enable
Attempt to create initial devicesfile through pvcreate with PVs/VGs
already in existence
pvcreate /dev/sda1
out
Physical volume "/dev/sda1" successfully created.
err
Not creating system devices file due to existing VGs.



SCENARIO - altered_devname_check_and_repair:  Test the discovery and
repair of an altered devname in devicesfile entry (bug
2039977|2040482)
Copying out altered system.devices file to
virt-494.cluster-qe.lab.eng.brq.redhat.com
/tmp/system4.devices ->
virt-494.cluster-qe.lab.eng.brq.redhat.com:/etc/lvm/devices/system.devices
lvmdevices --check
out

err
 Device /dev/sda1 has updated name (devices file /dev/sdz1)
 Updates needed for devices file.

lvmdevices --update
 Updated devices file to version 1.1.18



SCENARIO - altered_devname_w_pv_label_present_check_and_repair:  Test
for the alteration of the devicesfiles devname when a pv label exists
(2039977|2040482)
Altered entry:
IDTYPE=sys_wwid IDNAME=naa.60014051b30947a585d4632aee225072
DEVNAME=/dev/sda PVID=qJG0aOumNaFrurSXbYkVlqHAvC08sg3n PART=1
Copying out altered system.devices file to
virt-494.cluster-qe.lab.eng.brq.redhat.com
/tmp/system1440.devices ->
virt-494.cluster-qe.lab.eng.brq.redhat.com:/etc/lvm/devices/system.devices
path:/dev/sda1
lvmdevices --check
out

err
 Device /dev/sda1 has updated name (devices file /dev/sda)
 Updates needed for devices file.

lvmdevices --update
 Updated devices file to version 1.1.27




SCENARIO - alter_valid_deviceidtypes_to_no_longer_available_types:
Test how lvmdevices and lvm commands react to deviceidtypes that are
no longer valid post rh
el9.2 (bug 2128026)
lvmdevices -y --config devices/scan_lvs=1  --adddev /dev/sda1
Altered entry:
IDTYPE=mpath_uuid IDNAME=naa.60014051b30947a585d4632aee225072
DEVNAME=/dev/sda1 PVID=. PART=1
Copying out altered system.devices file to
virt-494.cluster-qe.lab.eng.brq.redhat.com
/tmp/system494.devices ->
virt-494.cluster-qe.lab.eng.brq.redhat.com:/etc/lvm/devices/system.devices
lvmdevices --check
out

err
Devices file mpath_uuid naa.60014051b30947a585d4632aee225072 PVID none
last seen on /dev/sda1 not found.




# RHEL9.4  (Warnings now reported to stdout)

SCENARIO - enabling_devicesfile_w_existing_vgs_present:  Create
initial PV with devicesfile newly turned ON, with VGs already in
existence prior to enablement
vgcreate    devfile_VG /dev/sde1 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sdf1
 Volume group "devfile_VG" successfully created

Enabling devicesfile on virt-245.cluster-qe.lab.eng.brq.redhat.com
Setting use_devicesfile to enable
Attempt to create initial devicesfile through pvcreate with PVs/VGs
already in existence
pvcreate /dev/sda1
out
Physical volume "/dev/sda1" successfully created.
 Not creating system devices file due to existing VGs.
err

pvcreate should have warned that a system devices file is not being
created in this scenario



SCENARIO - altered_devname_check_and_repair:  Test the discovery and
repair of an altered devname in devicesfile entry (bug
2039977|2040482)
Copying out altered system.devices file to
virt-245.cluster-qe.lab.eng.brq.redhat.com
/tmp/system1940.devices ->
virt-245.cluster-qe.lab.eng.brq.redhat.com:/etc/lvm/devices/system.devices
lvmdevices --check
out
 IDTYPE=sys_wwid IDNAME=naa.6001405d1239da98b3940f793c2f827e
DEVNAME=/dev/sda1 (old /dev/sdz1) PVID=none PART=1: update

err
 Updates needed for devices file.

lvmdevices should have noticed the name change



SCENARIO - altered_devname_w_pv_label_present_check_and_repair:  Test
for the alteration of the devicesfiles devname when a pv label exists
(2039977|2040482)
Altered entry:
IDTYPE=sys_wwid IDNAME=naa.60014051a51bc9c309348218a680e219
DEVNAME=/dev/sda PVID=gxu28KRd20AF22lr7ccQegp8XKmoppxh PART=1
Copying out altered system.devices file to
virt-125.cluster-qe.lab.eng.brq.redhat.com
/tmp/system766.devices ->
virt-125.cluster-qe.lab.eng.brq.redhat.com:/etc/lvm/devices/system.devices
path:/dev/sda1
lvmdevices --check
out
 IDTYPE=sys_wwid IDNAME=naa.60014051a51bc9c309348218a680e219
DEVNAME=/dev/sda1 (old /dev/sda) PVID=gxu28KRd20AF22lr7ccQegp8XKmoppxh
PART=1: update

err
 Updates needed for devices file.

lvmdevices should have noticed the devname change



SCENARIO - alter_valid_deviceidtypes_to_no_longer_available_types:
Test how lvmdevices and lvm commands react to deviceidtypes that are
no longer valid post rh
el9.2 (bug 2128026)
lvmdevices -y --config devices/scan_lvs=1  --adddev /dev/sda1
Altered entry:
IDTYPE=mpath_uuid IDNAME=naa.60014051a51bc9c309348218a680e219
DEVNAME=/dev/sda1 PVID=gxu28KRd20AF22lr7ccQegp8XKmoppxh PART=1
Copying out altered system.devices file to
virt-125.cluster-qe.lab.eng.brq.redhat.com
/tmp/system1898.devices ->
virt-125.cluster-qe.lab.eng.brq.redhat.com:/etc/lvm/devices/system.devices
lvmdevices --check
out
IDTYPE=mpath_uuid IDNAME=naa.60014051a51bc9c309348218a680e219
DEVNAME=/dev/sda1 PVID=gxu28KRd20AF22lr7ccQegp8XKmoppxh PART=1: device
not found
err

lvmdevices should have noticed the invalid IDTYPE