Comment 19 for bug 1789650

Revision history for this message
Rod Smith (rodsmith) wrote :

I'm afraid the node is failing to deploy with those changes to /etc/maas/preseeds/curtin_userdata (I assume that's where you wanted them):

        Running command ['unshare', '--fork', '--pid', '--', 'chroot', '/tmp/tmpzfw22u7e/target', 'sh', '-c', 'ls -al /sys/firmware/efi\nbcurrent=$(ls /sys/firmware/efi/efivars/BootCurrent*)\n[ -e "${bcurrent}" ] && hexdump $bcurrent\n'] with allowed return codes [0] (capture=False)
        total 0
        drwxr-xr-x 5 root root 0 Sep 13 23:10 .
        drwxr-xr-x 6 root root 0 Sep 13 23:08 ..
        -r--r--r-- 1 root root 4096 Sep 13 23:10 config_table
        dr-xr-xr-x 2 root root 0 Sep 13 23:08 efivars
        -r--r--r-- 1 root root 4096 Sep 13 23:10 fw_platform_size
        -r--r--r-- 1 root root 4096 Sep 13 23:10 fw_vendor
        -r--r--r-- 1 root root 4096 Sep 13 23:10 runtime
        drwxr-xr-x 9 root root 0 Sep 13 23:10 runtime-map
        -r-------- 1 root root 4096 Sep 13 23:09 systab
        drwxr-xr-x 70 root root 0 Sep 13 23:10 vars
        ls: cannot access '/sys/firmware/efi/efivars/BootCurrent*': No such file or directory
        Running command ['udevadm', 'settle'] with allowed return codes [0] (capture=False)
        Running command ['umount', '/tmp/tmpzfw22u7e/target/sys'] with allowed return codes [0] (capture=False)
        Running command ['umount', '/tmp/tmpzfw22u7e/target/proc'] with allowed return codes [0] (capture=False)
        Running command ['umount', '/tmp/tmpzfw22u7e/target/dev'] with allowed return codes [0] (capture=False)
        finish: cmd-install/stage-late/02_hexdump/cmd-in-target: FAIL: curtin command in-target