Bug 1319319 - vgextend --restoremissing is misbehaving in certain case
Summary: vgextend --restoremissing is misbehaving in certain case
Keywords:
Status: NEW
Alias: None
Product: LVM and device-mapper
Classification: Community
Component: lvm2
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: LVM Team
QA Contact: cluster-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-18 19:57 UTC by Zdenek Kabelac
Modified: 2024-04-27 05:52 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:55:16 UTC
Embargoed:
rule-engine: lvm-technical-solution?
rule-engine: lvm-test-coverage?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 653643 0 medium CLOSED vgextend --restoremissing "passes" when just one of the multiple devices attempted works 2021-02-22 00:41:40 UTC

Internal Links: 653643

Description Zdenek Kabelac 2016-03-18 19:57:44 UTC
Description of problem:

While trying to fix some 'lvconvert --uncache' code - I've noticed the MISSING_PV behaves in weird way.

After longer research it's all bound to commit:
97e8048e05115c57a44ce7daba9992ff99d05d79
which was fix for the bugzilla #653643.

Here is minimalist test case (in lvm2 test suite words)
(3 devices are needed):
---
aux prepare_vg 3

lvcreate -l 1 -n lv1 $vg "$dev1"
lvcreate -l 1 -n lv2 $vg "$dev1"
lvcreate -l 1 -n lv3 $vg "$dev3"

aux disable_dev "$dev1"
lvremove -ff $vg/lv1
aux disable_dev "$dev2"
pvs

aux enable_dev "$dev1"
vgextend --restoremissing $vg "$dev1"
pvs

aux enable_dev "$dev2"
pvs
lvs -a -o+devices $vg
---


Version-Release number of selected component (if applicable):
2.02.146

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Jan Kurik 2016-07-26 04:37:10 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.

Comment 2 Fedora End Of Life 2017-11-16 19:36:38 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-12-12 10:55:16 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.