Comment 4 for bug 1961620

Spent a bit of time on this bug yesterday, the case is fairly unique in that the live server installer creates the partition layouts outside of cloud-init so cloud-init is unaware of the status of encrypted device status and failure to mount the /home dir. That said, cloud-init should probably minimally grow awareness of where there is a mount point /home defined for operations that are attempted to setup users in /home/* or import ssh keys etc. Additionally, cloud-init should probably be more aware of the status of any mount units defined by `systemd-fstab-generator`
certainly if those mount points are targets of cloud-init configuration changes.

Specifically if we are dealing with ssh key imports, user & group setup etc, cloud-init needs to be wary of of a failed /home/ or /home/* mount to avoid laying down configuration that would ultimately "disappear" of that failed mount get corrected by delayed user input.