ubuntue18.04 rear breaks on resolv.conf

[gdha]

Run rear -v mkbackup
Relax-and-Recover 2.4-git.0.f6a36de.unknown / 2019-03-26
Running rear mkbackup (PID 30354)
Using log file: /var/log/rear/rear-client.log
Using backup archive '/tmp/rear.rZqE11m2GXGutbA/outputfs/client/backup.tar.gz'
Using autodetected kernel '/boot/vmlinuz-4.15.0-29-generic' as kernel in the recovery system
Creating disk layout
Using guessed bootloader 'GRUB' (found in first bytes on /dev/sda)
Verifying that the entries in /var/lib/rear/layout/disklayout.conf are correct ...
Creating root filesystem layout
Adding biosdevname=0 to KERNEL_CMDLINE
Copying logfile /var/log/rear/rear-client.log into initramfs as '/tmp/rear-client-partial-2019-03-27T10:34:35+01:00.log'
Copying files and directories
Copying binaries and libraries
Copying all kernel modules in /lib/modules/4.15.0-29-generic (MODULES contains 'all_modules')
Omit copying files in /lib*/firmware/ (FIRMWARE_FILES='no')
Exiting rear mkbackup (PID 30354) and its descendant processes ...
Running exit tasks


Please check the rear logging /var/log/rear/rear-client.log
The last 25 lines are:
removed '/tmp/rear.rZqE11m2GXGutbA/rootfs/usr/lib/systemd/system/udev-trigger.service'
2019-03-27 10:35:12.472224278 Including build/GNU/Linux/620_verify_os_release_file.sh
'/etc/os-release' -> '/tmp/rear.rZqE11m2GXGutbA/rootfs/etc/os-release'
2019-03-27 10:35:12.512957919 Including build/GNU/Linux/630_simplify_systemd_reboot_halt_poweroff_shutdown.sh
2019-03-27 10:35:12.559737574 Including build/GNU/Linux/630_verify_resolv_conf_file.sh
'/etc/resolv.conf' -> '/tmp/rear.rZqE11m2GXGutbA/rootfs/etc/resolv.conf'
2019-03-27 10:35:12.567939415 Useless loopback nameserver '127.0.0.53' in /tmp/rear.rZqE11m2GXGutbA/rootfs/etc/resolv.conf
2019-03-27 10:35:12.673043733 ERROR: No nameserver or only loopback addresses in /tmp/rear.rZqE11m2GXGutbA/rootfs/etc/resolv.conf, specify a real nameserver via USE_RESOLV_CONF
===== Stack trace =====
Trace 0: /usr/sbin/rear:541 main
Trace 1: /usr/share/rear/lib/mkbackup-workflow.sh:15 WORKFLOW_mkbackup
Trace 2: /usr/share/rear/lib/framework-functions.sh:116 SourceStage
Trace 3: /usr/share/rear/lib/framework-functions.sh:56 Source
Trace 4: /usr/share/rear/build/GNU/Linux/630_verify_resolv_conf_file.sh:100 source
=== End stack trace ===
2019-03-27 10:35:12.683915121 Exiting rear mkbackup (PID 30354) and its descendant processes ...
2019-03-27 10:35:15.827025733 rear,30354 /usr/sbin/rear -v mkbackup
  `-rear,4466 /usr/sbin/rear -v mkbackup
      `-pstree,4467 -Aplau 30354
/usr/share/rear/lib/_input-output-functions.sh: line 146: kill: (4470) - No such process
2019-03-27 10:35:15.847703866 Running exit tasks
2019-03-27 10:35:15.849534521 Finished in 43 seconds
2019-03-27 10:35:15.850939021 Removing build area /tmp/rear.rZqE11m2GXGutbA
removed directory '/tmp/rear.rZqE11m2GXGutbA'
2019-03-27 10:35:16.133651210 End of program reached

ERROR: Check yourself via 'vagrant ssh client'
Aborting due to an error, check /export/rear-tests/logs/2019-03-27_10-33-29/rear-automated-test.sh.log for details

[gdha]

2019-03-27 15:41:26.668549939 Begin create_fs( fs:/ )
/usr/share/rear/lib/_input-output-functions.sh: line 457: type: tune4fs: not found
2019-03-27 15:41:26.672150410 Begin mount_fs( fs:/ )

to be checked

[gdha]

See also issues rear/rear#2015 and rear/rear#2018

[github-actions]

Stale issue message