Leapp fails with a mount error

Solution Verified - Updated -

Issue

  • The following errors can be seen during the reboot step:

    ~~~
    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
    ~~~
    

    Or

    ~~~
    2024-03-12 14:09:48.818 DEBUG    PID: 397 leapp.workflow.InitRamStart.remove_upgrade_boot_entry: External command has started: ['/bin/mount', '-a']
    2024-03-12 14:09:48.827 DEBUG    PID: 397 leapp.workflow.InitRamStart.remove_upgrade_boot_entry: mount: ext4: mount point does not exist.
    2024-03-12 14:09:48.831 DEBUG    PID: 397 leapp.workflow.InitRamStart.remove_upgrade_boot_entry: Command ['/bin/mount', '-a'] failed with exit code 32.
    ~~~
    

Environment

  • Red Hat Enterprise Linux 7, 8
    • leapp

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content