mount generators fail when rebased from Atomic Host/Silverblue about fedora-coreos-config HOT 2 CLOSED

This is probably an unsupported migration path, but I have a system that was running fedora silverblue, planning to rebase it to fedora coreos afterwards. I rebased it today and I have issues with /boot not mounting properly.

I think in theory FAH/Silverblue could be migrated to FCOS, but it's unlikely we will develop much tooling to make that easier. So yeah, probably not a supported migration path. :)

The partitioning is different and a lot of booting implementation details are different. There's also various dependencies between the source configs (this repo) and coreos-assembler, which would just be missed if you rebase from an Anaconda-based system. You really want to be in a supported known starting state so that automatic updates are reliable.

Specifically to the problem you're seeing though, I'm not sure offhand why there are different behaviours around /tmp between the two. They both use tmp-is-dir nowadays so /tmp should definitely exist in early boot.

from fedora-coreos-config.

Thanks @mildred for the report. Since this is an unsupported migration path I'm going to close this out. Feel free to re-open if we think there are other bugs that are exposed here that need to be chased down.

from fedora-coreos-config.