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 1747431

Summary: Rescue dies while mounting file systems on /mnt/sysimage when a NFS file system is present in /etc/fstab
Product: Red Hat Enterprise Linux 8 Reporter: Renaud Métrich <rmetrich>
Component: python-blivetAssignee: Vojtech Trefny <vtrefny>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.1CC: ajschult784, jikortus, jkonecny, jshivers, jstodola, mkielian, vtrefny
Target Milestone: rcKeywords: Reopened
Target Release: 8.0Flags: pm-rhel: mirror+
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: python-blivet-3.2.2-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-04 03:22:23 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:
Attachments:
Description Flags
Screenshot of backtrace none

Description Renaud Métrich 2019-08-30 12:31:49 UTC
Created attachment 1609838 [details]
Screenshot of backtrace

Description of problem:

Trying to recover a system installed with LVM Thin Provisioning only, the Rescue fails while trying to mount the file systems on /mnt/sysimage/* (Root on /mnt/sysimage succeeded) with following error (see attachment):

  TypeError: unsupported operand type(s) for +: 'method' and 'list'


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

anaconda 29.19.1.6 (RHEL8.1 beta), also seen with RHEL8 DVD


How reproducible:

Always


Steps to Reproduce:
1. Install a system with LVM Thin Provisioning and multiple filesystems:

  /
  /var
  /home
  /tmp
  swap

  (Not sure how many file systems are needed)

2. Boot in Rescue and hit 1) Continue


Actual results:

  /mnt/sysimage is mounted, but not the rest
  Anaconda dies


Expected results:

  No issue

Comment 1 Jiri Konecny 2019-09-02 07:56:27 UTC
Based on the traceback this is happening inside of our storage library. Switching components.

Comment 2 Jan Stodola 2020-04-20 18:54:23 UTC
Renaud, are you still able to reproduce the problem?
I wasn't able to reproduce it on a system installed using the following kickstart file:

text
keyboard --vckeymap=us --xlayouts='us'
lang en_US.UTF-8
rootpw redhat
timezone Europe/Prague --isUtc
reboot

# Disk partitioning information
clearpart --all --initlabel
bootloader --location=mbr
reqpart --add-boot
part pv.01 --size=8000
volgroup vg pv.01
logvol none --name=pool --vgname=vg --thinpool --size=1 --grow
logvol swap --fstype=swap --name=swap --vgname=vg --thin --poolname=pool --size=1000
logvol / --name=root --vgname=vg --thin --poolname=pool --size=3000 --grow
logvol /home --name=home --vgname=vg --thin --poolname=pool --size=1000
logvol /tmp --name=tmp --vgname=vg --thin --poolname=pool --size=1000
logvol /var --name=var --vgname=vg --thin --poolname=pool --size=1000

%packages
@base
%end

I tried RHEL-8.1 Beta and the latest 8.2, but no luck. Any hint would be welcome.
Thank you.

Comment 3 Renaud Métrich 2020-04-21 07:33:21 UTC
This works now with RHEL 8.1.0 DVD.
Let's close this.

Comment 4 Vojtech Trefny 2020-04-21 07:39:44 UTC
I think this should already be fixed in upstream, there was a problem in blivet's code discovered by a static analysis tool that could cause this, but it's not fixed in RHEL 8 yet. I think you need to have an NFS mount in /etc/fstab to trigger this.

Comment 5 Renaud Métrich 2020-04-21 08:24:08 UTC
Hi Vojtech,

You are right, this reproduces when having a NFS mount in /etc/fstab:

rmetrich:/home  /nfs_home  nfs  defaults 0 0


In fact this seems not related to Thin Pool at all, but having a NFS mount.

Comment 6 Jan Stodola 2020-04-21 09:33:53 UTC
Thanks, I can confirm that nfs mount in /etc/fstab causes this problem.

Comment 14 errata-xmlrpc 2020-11-04 03:22:23 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 (python-blivet bug fix and enhancement update), 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-2020:4728