Comment 13 for bug 1969971

> This is all good until nova-compute needs to do a vm resize and the
> image used to build the vm no longer exists in Glance. At which point
> Nova will use the instance.hostname from the database to perform an scp
> from source to destination and this fails because this hostname (fqdn
> from management network) is not in known_hosts.
>
> This is something that Nova should ultimately have support for but in
> the interim the suggestion is that nova-cloud-controller always adds
> the management network fqdn to known_hosts.

Ah, I reported the following one in the upstream before where Nova doesn't respect the live migration network specified in nova.conf. It was about copying the content of the config drive using scp executed from the target node.
https://bugs.launchpad.net/nova/+bug/1939869

At that point, we had a clear workaround that using vfat instead of iso9660 can avoid the scp code path in Nova. But it's good to know that it is the case mentioned above (image no longer available in Glance).