Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2125023

Summary: improve handling of duplicate vgids
Product: Red Hat Enterprise Linux 8 Reporter: Corey Marthaler <cmarthal>
Component: lvm2Assignee: LVM Team <lvm-team>
lvm2 sub component: Devices, Filtering and Stacking QA Contact: cluster-qe <cluster-qe>
Status: CLOSED MIGRATED Docs Contact:
Severity: high    
Priority: high CC: agk, cmarthal, heinzm, jbrassow, mcsontos, msnitzer, prajnoha, teigland, thornber, zkabelac
Version: 8.7Keywords: MigratedToJIRA, Triaged
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2040456 Environment:
Last Closed: 2023-09-23 18:35:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2040456    
Bug Blocks:    

Comment 3 Corey Marthaler 2022-09-07 18:46:11 UTC
I can't remember if this was to be fixed in rhel8 as well?

kernel-4.18.0-417.el8    BUILT: Wed Aug 10 15:40:43 CDT 2022
lvm2-2.03.14-6.el8    BUILT: Fri Jul 29 05:40:53 CDT 2022
lvm2-libs-2.03.14-6.el8    BUILT: Fri Jul 29 05:40:53 CDT 2022




SCENARIO - duplicate_vg_uuids_with_devicesfile_disabled:  Test how LVM reacts to PVs having the same pv and vg uuids while devicesfile is disabled (bug 2040456) 
adding entry to the devices file for /dev/sdb1
creating PV on hayes-01 using device /dev/sdb1
pvcreate --yes -ff   /dev/sdb1
  Physical volume "/dev/sdb1" successfully created.
creating VG on hayes-01 using PV(s) /dev/sdb1
vgcreate    df /dev/sdb1
  Volume group "df" successfully created

Disabling devicesfile on hayes-01
Setting use_devicesfile to disable
  PV /dev/sdb1   VG df              lvm2 [<1.82 TiB / <1.82 TiB free]
  Total: 1 [<1.82 TiB] / in use: 1 [<1.82 TiB] / in no VG: 0 [0   ]

Copying header from /dev/sdb1 to /dev/sdc1 on hayes-01
1+0 records in
1+0 records out
1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.0284696 s, 36.8 MB/s
Re-scanning lvm PVs (pvscan --cache)
  pvscan[441785] PV /dev/sdb1 online.

Disabling device sdb on hayes-01
'echo offline > /sys/block/sdb/device/state'
  VG #PV #LV #SN Attr   VSize  VFree 
  df   1   0   0 wz--n- <1.82t <1.82t
Renaming df to df_2
vgrename --yes df df_2
  Volume group "df" successfully renamed to "df_2"

Generating a new PV uuid for /dev/sdc1
pvchange -u /dev/sdc1

Enabling device sdb on hayes-01
'echo running > /sys/block/sdb/device/state'
WARNING: ignoring metadata seqno 1 on /dev/sdb1 for seqno 3 on /dev/sdc1 for VG df_2.
  WARNING: Inconsistent metadata found for VG df.
  See vgck --updatemetadata to correct inconsistency.
  Internal error: vginfo_lookup vgid KGHXvEiGocST9XkZcb747ypiK691UQ1Y has two names df df_2
  Internal error: lvmcache_update_vg df_2 no vginfo
  Internal error: vginfo_lookup vgid KGHXvEiGocST9XkZcb747ypiK691UQ1Y has two names df df_2
  Internal error: lvmcache_get_outdated_mdas no vginfo
  Internal error: vginfo_lookup vgid KGHXvEiGocST9XkZcb747ypiK691UQ1Y has two names df df_2
  Internal error: lvmcache_get_outdated_mdas no vginfo
pvs should warn about the need to fix the dup VGID

[root@hayes-01 ~]# pvscan
  WARNING: ignoring metadata seqno 1 on /dev/sdb1 for seqno 3 on /dev/sdc1 for VG df_2.
  WARNING: Inconsistent metadata found for VG df.
  See vgck --updatemetadata to correct inconsistency.
  Internal error: vginfo_lookup vgid KGHXvEiGocST9XkZcb747ypiK691UQ1Y has two names df df_2
  Internal error: lvmcache_update_vg df_2 no vginfo
  Internal error: vginfo_lookup vgid KGHXvEiGocST9XkZcb747ypiK691UQ1Y has two names df df_2
  Internal error: lvmcache_get_outdated_mdas no vginfo
  Internal error: vginfo_lookup vgid KGHXvEiGocST9XkZcb747ypiK691UQ1Y has two names df df_2
  Internal error: lvmcache_get_outdated_mdas no vginfo
  PV /dev/sdc1   VG df_2            lvm2 [<1.82 TiB / <1.82 TiB free]
  Total: 1 [<1.82 TiB] / in use: 1 [<1.82 TiB] / in no VG: 0 [0   ]

Comment 5 RHEL Program Management 2023-09-23 18:22:23 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 6 RHEL Program Management 2023-09-23 18:35:29 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.