Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-24876

[Bug] Rear recover fails with "ERROR: Could not create build area"

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Undefined Undefined
    • None
    • rhel-9.3.0
    • rear
    • Normal
    • sst_cs_system_management
    • ssg_core_services
    • False
    • Hide

      None

      Show
      None
    • Red Hat Enterprise Linux
    • x86_64

      What were you trying to do that didn't work?

      Rear recover after taking successful backup.

      Please provide the package NVR for which bug is seen:

      rear-2.6-20.el9_3.x86_64

      How reproducible:

      Always.

      Steps to reproduce

      1.  Create a 'ReaR' backup with parameter to export TMPDIR in '/'.
        ~~~
         cat /etc/rear/site.conf 
        OUTPUT=ISO
        OUTPUT_URL=nfs://X.X.X.X/rear
        BACKUP=NETFS
        BACKUP_URL=nfs://X.X.X.X/rear
        BACKUP_PROG_EXCLUDE=("${BACKUP_PROG_EXCLUDE[@]}" '/media' '/var/tmp' '/var/crash' '/ISO')
        NETFS_KEEP_OLD_BACKUP_COPY=n
        AUTOEXCLUDE_MULTIPATH=n
        export TMPDIR="/ISO"                                                      <========
        ONLY_INCLUDE_VG=( "rhel" )
        ~~~
      1. Try to recover with backup taken with above configuration by booting with rear ISO file, it fails with "ERROR: Could not create build area"  and fails to mount /ISO TMPDIR in recovery.

      WORKAROUND : 
      =============

      • Create  TMPDIR in rescue shell before recovering server. 
        ~~~
        #mkdir /ISO
        #rear recover -vD                                        <=== Runs successfully.
        ~~~

        Expected results

      To successfully proceed to recover the backup taken.

      Actual results

      ERROR: Could not create build area

            rhn-support-pcahyna Pavel Cahyna
            rhn-support-ppaddhar Paras Paddhariya
            Pavel Cahyna Pavel Cahyna
            rhel-cs-system-management-subsystem-qe Bot rhel-cs-system-management-subsystem-qe Bot
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: