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.
Description of problem:
The lvm devices which are created using python-blivet becomes invisible to pvs or vgs and appears only after vgscan. This does not happens once we run vgscan
And also sometimes when we empty the disk device using dd command and create lvm out of it, we observed the created lvm devices became visible to vgs only after 1 or 2 minutes. This happens in a plain RHEL6 node it has only python-blivet installed.
Version-Release number of selected component (if applicable):
lvm2-2.02.118-2.el6.x86_64
lvm2-libs-2.02.118-2.el6.x86_64
python-blivet-1.0.0.1-1.el6rhs.noarch
Red Hat Enterprise Linux Server release 6.7 Beta (Santiago)
How reproducible:
Always till we run vgscan atleast one time
Actual results:
Create pv, vg, lv successfully. However it does not appear when we
run vgs or lvs or use python-blivet to list the devices
I assume it could be related to the fact, that python API is rather not actively maintained and user should stay with executing 'real' lvm2 commands.
Python API should be only used as replacement for 'lvs'.
As a 'workaround' maybe you could try to disable usage of lvmetad and stop using this daemon (since the timing could be related to the fact devices are discovered later by udev)
Hi!
I'm not sure what Python API you are referring to.
In this context, python-blivet, which is actively maintained, is in the typical situation of executing lvm commands via a python subprocess call.
- mulhern
Ok - from the description it seemed like it's describing problem from using liblvm2app and it's python binding from lvm2.
So in case blivet calls real lvm2 commands - please provide full '-vvvv' of lvcreate command trace executed via Python Blivet API.
Then please show 'lvs' after such command (so we could see LV is really missing)
and 'dmsetup table' (so we could see it's really present & active).
Also attach your lvm.conf please.
This looks like an issue with .cache file at first glance - we've done some fixes in this area already. For starters, is this reproducible with latest z-stream lvm2-2.02.118-3.el6_7.3 ?
(In reply to Peter Rajnoha from comment #7)
> This looks like an issue with .cache file at first glance - we've done some
> fixes in this area already. For starters, is this reproducible with latest
> z-stream lvm2-2.02.118-3.el6_7.3 ?
Is this still reproducible with recent versions of lvm2?
Alternatively - is this reproducible when you have devices/obtain_device_list_from_udev=1 set in lvm.conf?
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
The official life cycle policy can be reviewed here:
http://redhat.com/rhel/lifecycle
This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:
https://access.redhat.com/
Comment 13Red Hat Bugzilla
2023-09-14 03:00:29 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days