Instead of separately logging which systemd units are stuck and failed, just include it in the fatal error we eventually emit when we print the test failure. Otherwise it's not easy to match logged messages with failures when running tests in parallel.
@jlebon: Overrode contexts on behalf of jlebon: ci/prow/rhcos
In response to [this](https://github.com/coreos/coreos-assembler/pull/3823#issuecomment-2186999151):
>/override ci/prow/rhcos
Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
Instead of separately logging which systemd units are stuck and failed, just include it in the fatal error we eventually emit when we print the test failure. Otherwise it's not easy to match logged messages with failures when running tests in parallel.