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:
Leapp fails while running "mount -a" when there is a CIFS entry in /etc/fstab.
It's likely due to the DNS resolution. This kind of entries could be ignored, like NFS ones.

Version-Release number of selected component (if applicable):
leapp-repository-0.11.0-4.el7_9.noarch

How reproducible:
100% for the customer

Steps to Reproduce:
1. Add a CIFS entry with a hostname in /etc/fstab
2. Proceed to the upgrade

Actual results:
upgrade[679]: CalledProcessError: Command ['/bin/mount', '-a'] failed with exit code 32.
:
upgrade[679]: Container sysroot failed with error code 1.
upgrade[679]: writing logs to disk and rebooting
upgrade[679]: /bin/upgrade: line 19: /sysroot/var/tmp/system-upgrade.state: Read-only file system
systemd[1]: upgrade.service: Main process exited, code=exited, status=1/FAILURE
:
upgrade[1951]: mount error: could not resolve address for ab.cd.ef.net: Unknown error

Additional info:
Commenting out this entry for the time of the upgrade easily fixes the issue.

Currently, we require all partitions in /etc/fstab has to be local and mountable using "mount -a" for the upgrade. CIFS doesn't meet this condition by nature of CIFS. Until the networking will be working during the "upgrade initramfs" phases, only valid (and duable) solution from our side I can see is detection of CIFS and inhibit the upgrade. Only valid way for user in this case (and expected now) is to comment out CIFS partitions in /etc/fstab before the upgrade (before the run of `leapp upgrade`) and set it back after the upgrade.

Thanks Petr for modifying the expectation, yes it should be inhibited.

The PR with the fix:
    https://github.com/oamg/leapp-repository/pull/632

unfortunately, regarding the current deadline, we are not sure whether the fix will be present in the upcoming release.

The fix has been merged in the upstream, so it will be part of the next release.

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 (leapp, leapp-repository, and cockpit-leapp 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-2021:4603