Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-133145

'vgchange --persist start --removekey' fails in starting desired new key, but does succeed in removing current mismatched key

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Undefined Undefined
    • None
    • rhel-10.2
    • lvm2
    • None
    • None
    • None
    • rhel-storage-lvm
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • x86_64
    • None

      This is similar to the type of issue as https://issues.redhat.com/browse/RHEL-115111 however using the high level management vgchange cmd as the interface. The issue is the 'vgchange --persist start --removekey' is unable to start with the new key in one go.

      kernel-6.12.0-157.el10    BUILT: Thu Nov 13 01:02:26 PM CET 2025
      lvm2-2.03.36-1.el10    BUILT: Sat Oct 25 04:42:32 AM CEST 2025
      lvm2-libs-2.03.36-1.el10    BUILT: Sat Oct 25 04:42:32 AM CEST 2025
       
       
      [root@virt-503 ~]# lvmpersist read-keys --vg persist_VG
      Device /dev/sde: registered keys: 0x9fe0f509ef4d1320
      Device /dev/sdc: registered keys: 0x9fe0f509ef4d1320
      Device /dev/sdb: registered keys: 0x9fe0f509ef4d1320
      Device /dev/sda: registered keys: 0x9fe0f509ef4d1320
      Device /dev/sdd: registered keys: 0x9fe0f509ef4d1320
       
      # Differing key currently exists on devices than in lvmlocal
      [root@virt-503 ~]# grep pr_key /etc/lvm/lvmlocal.conf 
              # Configuration option local/pr_key.
              # 0x prefix. If pr_key is not set, host_id will be used to create a key.
              pr_key = "0x9fe0f509ef4d1440"   # edited by QA Wed Dec  3 18:08:03 2025
       
      # Generic start wont work as expected
      [root@virt-503 ~]#  vgchange --persist start persist_VG
        persistent reservation is started by another key (0x9fe0f509ef4d1320)
       
      # Start attempt with --removekey "fails", but it does remove the key, thus allowing an additional generic start attempt to be successful
      [root@virt-503 ~]# vgchange --persist start --removekey 0x9fe0f509ef4d1320 persist_VG
        lvmpersist: start persist_VG failed to preempt-abort 0x9fe0f509ef4d1320 on /dev/sda.
        persistent reservation start failed: lvmpersist command error.
      [root@virt-503 ~]# lvmpersist read-keys --vg persist_VG
      Device /dev/sde: registered keys: none
      Device /dev/sdc: registered keys: none
      Device /dev/sdb: registered keys: none
      Device /dev/sda: registered keys: none
      Device /dev/sdd: registered keys: none
       
      # Generic start can now add the new key
      [root@virt-503 ~]# vgchange --persist start persist_VG
        lvmpersist: started persist_VG with key 0x9fe0f509ef4d1440.
       
      [root@virt-503 ~]# lvmpersist read-keys --vg persist_VG
      Device /dev/sde: registered keys: 0x9fe0f509ef4d1440
      Device /dev/sdc: registered keys: 0x9fe0f509ef4d1440
      Device /dev/sdb: registered keys: 0x9fe0f509ef4d1440
      Device /dev/sda: registered keys: 0x9fe0f509ef4d1440
      

              lvm-team lvm-team
              cmarthal@redhat.com Corey Marthaler
              lvm-team lvm-team
              Cluster QE Cluster QE
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: