Dusty Mabe

This open issue is generically an RFE for systemd for being able to depend or hook into system units from a user unit. The specific use case (for me) that...

> The specific use case (for me) that brings this to the top is when I'm trying to run rootless containers that depend on the network via a systemd user...

> IIUC, the main objection of the bug is less about presence of the new commit from the upgrade --preview, but the absence of the previous deployed commit in the...

> Huh, okay. I guess this is because it's jumping ahead by several commits (25.148 -> 25.154), leaving a gap in the local chain of commits? right, i believe that...

> I can look into this if it'd be handy to have. thanks robert. Funny enough, I actually hit this again today. @cgwalters I know we just discussed that labeling...

hmm. I wonder if https://github.com/ostreedev/ostree/pull/2847 means we can close this? or at least modify the scope.

I think the tests are usually run inside the COSA container after it's been built: i.e. ``` podman build -t localhost/coreos-assembler:latest . ``` Then: ``` podman run -it --rm --userns...

The https://github.com/coreos/fedora-coreos-config/blob/testing-devel/tests/kola/upgrade/extended/test.sh part of this was covered in: - https://github.com/coreos/fedora-coreos-config/commit/22d6552936951df9899a39c2e62d78ee27194f02 - https://github.com/coreos/fedora-coreos-config/commit/a10a39d09d645a9f8bd886e73a2c5949faf1185b

I'd say let's not worry about this for now and we'll get the checkMachine bits when (if) we fold testiso into the regular kola tests. We can open a new...

I'll note here that I've seen this too and have been able to reproduce on both F38 and F39. I think what is happening here is that previously (before https://github.com/osbuild/osbuild/commit/28c2772d42159ccdf07b629509dbaf23ebb61f68)...