The final "ready" is the check for /var/lib/cloud/instance/boot-finished anyway.
So indeed this now entering an infinite loop just blocks it from ever learning about it. "systemctl is-system-running" is more trustworthy indeed and even has he feature we'd wait without polling. From [1]: "Use --wait to wait until the boot process is completed before printing the current state and returning the appropriate error status. If --wait is in use, states initializing or starting will not be reported, instead the command will block until a later state (such as running or degraded) is reached." We do not even need to check the state, it will wait in the phases that are too early, and then look for the cloud init stamp in the second step. That --wait is available since the systemd in Focal, but we should go by >=Plucky to avoid changing behavior anyway. [1]: https://www.freedesktop.org/software/systemd/man/latest/systemctl.html#is- system-running -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2095042 Title: uvt-kvm remote-wait-script doesn't work from Plucky onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/2095042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
