What were you trying to do that didn't work?

[root@grant-01 ~]# grep devicesfile /etc/lvm/lvm.conf
        use_devicesfile = 0     # edited by QA Thu Aug 24 01:02:26 2023

[root@grant-01 ~]# vdo create --force --name lvm_import_vdo_sanity
--vdoLogicalSize 50G --device /dev/sdb
Creating VDO lvm_import_vdo_sanity
      The VDO volume can address 444 GB in 222 data slabs, each 2 GB.
      It can grow to address at most 16 TB of physical storage in 8192 slabs.
      If a larger maximum size might be needed, use bigger slabs.
Starting VDO lvm_import_vdo_sanity
Starting compression on VDO lvm_import_vdo_sanity
VDO instance 13 volume is ready at /dev/mapper/lvm_import_vdo_sanity
[root@grant-01 ~]# lvm_import_vdo --yes --name
vdovg/lvm_import_vdo_sanity /dev/sdb
Stopping VDO lvm_import_vdo_sanity
Converting VDO lvm_import_vdo_sanity
      Checking device
      Non converted VDO. Converting to LVM
      Opening /dev/mapper/VDO_lvm_import_vdo_2578777563_snap exclusively
      Loading the VDO superblock and volume geometry
      Checking the VDO state
      New geometry block offset calculated at 1925120
      Converting the UDS index
      Converting the VDO
      Conversion completed for
'/dev/mapper/VDO_lvm_import_vdo_2578777563_snap': VDO is now aligned
on 1048576 bytes, starting at offset 1925120
  Physical volume "/dev/mapper/VDO_lvm_import_vdo_2578777563_snap"
successfully created.
  Volume group "vdovg" successfully created
  WARNING: Logical volume vdovg/lvm_import_vdo_sanity_vpool not zeroed.
  Logical volume "lvm_import_vdo_sanity_vpool" created.
  WARNING: Converting logical volume vdovg/lvm_import_vdo_sanity_vpool
to VDO pool volume WITHOUT formating.
  WARNING: Using invalid VDO pool data MAY DESTROY YOUR DATA!
  Logical volume "lvm_import_vdo_sanity" created.
  Converted vdovg/lvm_import_vdo_sanity_vpool to VDO pool volume and
created virtual vdovg/lvm_import_vdo_sanity VDO volume.
  0 logical volume(s) in volume group "vdovg" now active
  Volume group "vdovg" successfully changed
  Volume group "vdovg" successfully changed
[root@grant-01 ~]# echo $?
0

[root@grant-01 ~]# grep devicesfile /etc/lvm/lvm.conf
        use_devicesfile = 1     # edited by QA Thu Aug 24 01:02:26 2023

[root@grant-01 ~]# vdo create --force --name lvm_import_vdo_sanity
--vdoLogicalSize 50G --device /dev/sdb
Creating VDO lvm_import_vdo_sanity
      The VDO volume can address 444 GB in 222 data slabs, each 2 GB.
      It can grow to address at most 16 TB of physical storage in 8192 slabs.
      If a larger maximum size might be needed, use bigger slabs.
Starting VDO lvm_import_vdo_sanity
Starting compression on VDO lvm_import_vdo_sanity
VDO instance 19 volume is ready at /dev/mapper/lvm_import_vdo_sanity
[root@grant-01 ~]# lvm_import_vdo --yes --name
vdovg/lvm_import_vdo_sanity /dev/sdb
Stopping VDO lvm_import_vdo_sanity
Converting VDO lvm_import_vdo_sanity
      Checking device
      Non converted VDO. Converting to LVM
      Opening /dev/mapper/VDO_lvm_import_vdo_733978701_snap exclusively
      Loading the VDO superblock and volume geometry
      Checking the VDO state
      New geometry block offset calculated at 1925120
      Converting the UDS index
      Converting the VDO
      Conversion completed for
'/dev/mapper/VDO_lvm_import_vdo_733978701_snap': VDO is now aligned on
1048576 bytes, starting at offset 1925120
  Physical volume "/dev/mapper/VDO_lvm_import_vdo_733978701_snap"
successfully created.
  Volume group "vdovg" successfully created
  WARNING: Logical volume vdovg/lvm_import_vdo_sanity_vpool not zeroed.
  Logical volume "lvm_import_vdo_sanity_vpool" created.
  WARNING: Converting logical volume vdovg/lvm_import_vdo_sanity_vpool
to VDO pool volume WITHOUT formating.
  WARNING: Using invalid VDO pool data MAY DESTROY YOUR DATA!
  Logical volume "lvm_import_vdo_sanity" created.
  Converted vdovg/lvm_import_vdo_sanity_vpool to VDO pool volume and
created virtual vdovg/lvm_import_vdo_sanity VDO volume.
  0 logical volume(s) in volume group "vdovg" now active
  Volume group "vdovg" successfully changed
  Volume group "vdovg" not found
  Cannot process volume group vdovg
[root@grant-01 ~]# echo $?
5

+ verbose 'Merging converted VDO volume...'

+ test -z ''
+ VDO_INCONSISTENT=1
+ dmsetup resume VDO_lvm_import_vdo_67379073_snap
++ seq 1 20
+ for i in $(seq 1 20)
+ status=($("$DMSETUP" status "$VDO_DM_SNAPSHOT_NAME"))
++ dmsetup status VDO_lvm_import_vdo_67379073_snap
+ '[' 64 = 64 ']'
+ break
+ '[' 64 '!=' 64 ']'
+ VDO_INCONSISTENT=
+ VDO_CONFIG_RESTORE=
+ dmsetup remove VDO_lvm_import_vdo_67379073_snap
+ VDO_DM_SNAPSHOT_NAME=
+ losetup -d /dev/loop0
+ VDO_SNAPSHOT_LOOP=
+ verbose 'Merging of VDO device finished.'
+ test -z ''
++ lvm pvs /dev/disk/by-id/ata-HFS480G32FEH-BA10A_ESB1N6680I1501N6B
+ output='  Failed to find physical volume "/dev/sdb".'
+ grep -q 'not in devices file'
+ echo '  Failed to find physical volume "/dev/sdb".'
+ '[' -n --yes ']'
+ dry lvm vgchange --setautoactivation y vdovg
+ '[' 0 -ne 0 ']'
+ verbose Executing lvm vgchange --setautoactivation y vdovg
+ test -z ''
+ lvm vgchange --setautoactivation y vdovg
  Volume group "vdovg" not found
  Cannot process volume group vdovg
+ cleanup
+ RC=5
+ trap '' HUP INT QUIT ABRT TERM EXIT
+ '[' -z '' ']'
+ '[' -e '' ']'
+ '[' -n '' ']'
+ '[' -n '' ']'
+ '[' -z '' ']'
+ rm -rf /tmp/VDO_lvm_import_vdo_67379073
+ exit 5

Please provide the package NVR for which bug is seen:

kernel-4.18.0-511.el8    BUILT: Fri Aug 18 17:12:35 CEST 2023

lvm2-2.03.14-11.el8_9    BUILT: Thu Sep  7 21:47:30 CEST 2023
lvm2-libs-2.03.14-11.el8_9    BUILT: Thu Sep  7 21:47:30 CEST 2023