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

clean up the internal lvmlock LV in error paths

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

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • 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
    • None

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

       

      During testing I've noticed some instances in which the internal lvmlock LV is not deactivated after some command failures in one or more error paths (I suspect vgchange --lockstart).

      What is the impact of this issue to you?

      Please provide the package NVR for which the bug is seen:

      How reproducible is this bug?:

      Steps to reproduce

      1.  
      2.  
      3.  

      Expected results

      Actual results

              teigland@redhat.com David Teigland
              teigland@redhat.com David Teigland
              David Teigland David Teigland
              Corey Marthaler Corey Marthaler
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: