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 1554224 - deactivate active lvs on incomplete vgs during populate
Summary: deactivate active lvs on incomplete vgs during populate
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: python-blivet
Version: 7.5
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Blivet Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
: 1641055 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-12 06:25 UTC by xhe@redhat.com
Modified: 2021-09-03 14:12 UTC (History)
6 users (show)

Fixed In Version: python-blivet-0.61.15.70-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-30 11:37:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
anaconda-tb.log (1015.99 KB, text/plain)
2018-03-12 06:34 UTC, xhe@redhat.com
no flags Details
storage.log (203.62 KB, text/plain)
2018-03-12 06:45 UTC, xhe@redhat.com
no flags Details
program.log (40.47 KB, text/plain)
2018-03-12 06:47 UTC, xhe@redhat.com
no flags Details
messages.log (188.87 KB, text/plain)
2018-03-14 05:27 UTC, xhe@redhat.com
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3270 0 None None None 2018-10-30 11:39:35 UTC

Description xhe@redhat.com 2018-03-12 06:25:24 UTC
Description of problem:
IOException: Partition(s) 6 on /dev/mapper/360a9800042566643352b476d67496d44 have been written

Version-Release number of selected component (if applicable):
anaconda 21.48.22.134-1

How reproducible:
always

Steps to Reproduce:
1. Install RHEL-7.5-20180308.1 Server x86_64 on server with SAN disks
   Or you can clone this beaker job to reproduce the bug https://beaker.engineering.redhat.com/recipes/4914636#task69122614
2.
3.

Actual results:
****************snip*********************
Setting up the installation environment    
  
An unknown error has occured, look at the /tmp/anaconda-tb* file(s) for more details 
          
=============================================================================== 
An unknown error has occurred 
      
=============================================================================== 
anaconda 21.48.22.134-1 exception report 
Traceback (most recent call first): 
  File "/usr/lib64/python2.7/site-packages/parted/disk.py", line 213, in commit 
    return self.__disk.commit() 
  File "/usr/lib64/python2.7/site-packages/parted/decorators.py", line 41, in new 
    ret = fn(*args, **kwds) 
  File "/usr/lib/python2.7/site-packages/blivet/formats/disklabel.py", line 290, in commit 
    self.partedDisk.commit() 
  File "/usr/lib/python2.7/site-packages/blivet/devices/partition.py", line 687, in _destroy 
    self.disk.originalFormat.commit() 
  File "/usr/lib/python2.7/site-packages/blivet/devices/storage.py", line 525, in destroy 
    self._destroy() 
  File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 344, in execute 
    self.device.destroy() 
  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 373, in processActions 
    action.execute(callbacks) 
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 380, in doIt 
    self.devicetree.processActions(callbacks) 
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 230, in turnOnFilesystems 
    storage.doIt(callbacks)      
  
  File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 206, in doInstall 
    turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall, callbacks=callbacks_reg) 
  File "/usr/lib64/python2.7/threading.py", line 765, in run 
    self.__target(*self.__args, **self.__kwargs) 
  File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 227, in run 
    threading.Thread.run(self, *args, **kwargs) 
IOException: Partition(s) 6 on /dev/mapper/360a9800042566643352b476d67496d44 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes. 

What do you want to do now? 
1) Report Bug 
2) Debug 
3) Quit 
      
Please make your choice from above:       
****************snip*********************
       

Expected results:
anaconda works 

Additional info:

Comment 2 xhe@redhat.com 2018-03-12 06:34:06 UTC
Created attachment 1407074 [details]
anaconda-tb.log

Comment 3 xhe@redhat.com 2018-03-12 06:45:50 UTC
Created attachment 1407078 [details]
storage.log

Comment 4 xhe@redhat.com 2018-03-12 06:47:08 UTC
Created attachment 1407079 [details]
program.log

Comment 5 Jiri Konecny 2018-03-12 10:38:42 UTC
Looks like a storage related issue.
Changing components.

Comment 6 xhe@redhat.com 2018-03-14 05:27:59 UTC
Created attachment 1407816 [details]
messages.log

Comment 7 xhe@redhat.com 2018-03-14 05:31:02 UTC
I re-installed the RHEL-7.5 RC-1.1 RHEL-7.5-20180308.1 on the same server with san disk in [1], it's weird that I didn't see the issue, not sure how to reproduce it. But I will try to install it by manual and will response result later.

[1] PASS https://beaker.engineering.redhat.com/jobs/2371531

Comment 8 xhe@redhat.com 2018-03-14 08:48:31 UTC
I tried to install manually, I hit new issue below
https://bugzilla.redhat.com/show_bug.cgi?id=1555205

Comment 9 David Lehman 2018-03-20 14:17:00 UTC
The failure was triggered by a specific broken lvm configuration involving a missing physical volume. At the beginning of the successful installation there was no existing lvm layout on the disk at all.

Comment 10 David Lehman 2018-03-20 14:19:09 UTC
The root cause appears to be a fairly rare occurrence in which an lv is activated in an incomplete lvm volume group. Apparently that lv resides only on the non-missing pv(s). Blivet should deactivate such lvs explicitly in this case.

Comment 11 David Lehman 2018-03-20 14:45:11 UTC
Workaround is to clean up broken/incomplete/obsolete lvm metadata before performing the installation. Moving to 7.6.

Comment 14 David Lehman 2018-06-20 20:41:57 UTC
Updates image for testing of proposed fix:

  inst.updates=http://people.redhat.com/~dlehman/updates/incomplete_lvm.img


Please let me know how it goes.

Comment 15 David Lehman 2018-06-20 20:47:02 UTC
Upstream pull request:

  https://github.com/storaged-project/blivet/pull/703

Comment 16 Jan Stodola 2018-06-21 09:52:21 UTC
Updates image works fine, I'm no longer able to reproduce this bug.

Comment 18 Martin Banas 2018-08-08 10:27:11 UTC
Reproduced on RHEL-7.5 GA, verified on RHEL-7.6-Beta-1.0

Comment 19 David Lehman 2018-10-26 16:50:05 UTC
*** Bug 1641055 has been marked as a duplicate of this bug. ***

Comment 21 errata-xmlrpc 2018-10-30 11:37:14 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:3270


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