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:
When using rear to backup system, sometimes we need to work with NFS server that only supports NFSv3. We need to specify 'BACKUP_OPTIONS="nfsvers=3,nolock"' option in this situation.
But if we use rear in rescue mode, this option not work.
Version-Release number of selected component (if applicable):
rear-2.00-2.el7.x86_64
How reproducible:
After install and configure rear, boot the system into rescue mode and run
'rear mkbackup'.
Steps to Reproduce:
1. install rear and configure rear with the following configuration in /etc/rear/local.conf:
===
OUTPUT=ISO
OUTPUT_URL=nfs://192.168.122.1/home/storage
BACKUP=NETFS
BACKUP_OPTIONS="nfsvers=3,nolock"
BACKUP_URL=nfs://192.168.122.1/home/storage
BACKUP_PROG_EXCLUDE=("${BACKUP_PROG_EXCLUDE[@]}" '/media' '/var/tmp' '/var/crash')
===
2. test 'rear mkbackup' command, there is no problem
# rear -v mkbackup
3. boot system into rescue mode and run 'rear mkbackup'
# chroot /mnt/sysimage
# ip a
# nmcli con up ens32 --> configure the nic with proper ip address
# mount -t nfs -o 'nfsvers=3,nolock' 192.168.122.1:/home/storage /mnt
# umount /mnt
# rear -v mkbackup
Actual results:
It failed with following error:
ERROR: Mount command 'mount -v -t nfs -o rw,noatime 192.168.122.1:/home/storage /tmp/rear.UYwAxLnNr85F2kL/outputfs' failed.
Aborting due to an error, check /var/log/rear/rear-localhost.log for details.
Expected results:
'rear mkbackup' command can make the backup files successfully in rescue mode.
Red Hat Enterprise Linux 7 shipped it's final minor release on September 29th, 2020. 7.9 was the last minor releases scheduled for RHEL 7.
From intial triage it does not appear the remaining Bugzillas meet the inclusion criteria for Maintenance Phase 2 and will now be closed.
From the RHEL life cycle page:
https://access.redhat.com/support/policy/updates/errata#Maintenance_Support_2_Phase
"During Maintenance Support 2 Phase for Red Hat Enterprise Linux version 7,Red Hat defined Critical and Important impact Security Advisories (RHSAs) and selected (at Red Hat discretion) Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available."
If this BZ was closed in error and meets the above criteria please re-open it flag for 7.9.z, provide suitable business and technical justifications, and follow the process for Accelerated Fixes:
https://source.redhat.com/groups/public/pnt-cxno/pnt_customer_experience_and_operations_wiki/support_delivery_accelerated_fix_release_handbook
Feature Requests can re-opened and moved to RHEL 8 if the desired functionality is not already present in the product.
Please reach out to the applicable Product Experience Engineer[0] if you have any questions or concerns.
[0] https://bugzilla.redhat.com/page.cgi?id=agile_component_mapping.html&product=Red+Hat+Enterprise+Linux+7
Description of problem: When using rear to backup system, sometimes we need to work with NFS server that only supports NFSv3. We need to specify 'BACKUP_OPTIONS="nfsvers=3,nolock"' option in this situation. But if we use rear in rescue mode, this option not work. Version-Release number of selected component (if applicable): rear-2.00-2.el7.x86_64 How reproducible: After install and configure rear, boot the system into rescue mode and run 'rear mkbackup'. Steps to Reproduce: 1. install rear and configure rear with the following configuration in /etc/rear/local.conf: === OUTPUT=ISO OUTPUT_URL=nfs://192.168.122.1/home/storage BACKUP=NETFS BACKUP_OPTIONS="nfsvers=3,nolock" BACKUP_URL=nfs://192.168.122.1/home/storage BACKUP_PROG_EXCLUDE=("${BACKUP_PROG_EXCLUDE[@]}" '/media' '/var/tmp' '/var/crash') === 2. test 'rear mkbackup' command, there is no problem # rear -v mkbackup 3. boot system into rescue mode and run 'rear mkbackup' # chroot /mnt/sysimage # ip a # nmcli con up ens32 --> configure the nic with proper ip address # mount -t nfs -o 'nfsvers=3,nolock' 192.168.122.1:/home/storage /mnt # umount /mnt # rear -v mkbackup Actual results: It failed with following error: ERROR: Mount command 'mount -v -t nfs -o rw,noatime 192.168.122.1:/home/storage /tmp/rear.UYwAxLnNr85F2kL/outputfs' failed. Aborting due to an error, check /var/log/rear/rear-localhost.log for details. Expected results: 'rear mkbackup' command can make the backup files successfully in rescue mode.