Comment 4 for bug 1763766

Currently we allow rebuilding to a new image with different image properties, so we need to ensure that the new image properties take effect on a rebuild. For example, the new image could interact with the AggregateImagePropertiesIsolation or ImagePropertiesFilter scheduler filters so we need to ensure that these filters get run.

I'm not sure we need to skip hardware.numa_fit_instance_to_host() since I think it's okay if the topology as seen by the guest is changed over a rebuild.

The important thing is that the resource consumption as seen by nova and reported in placement can't change. So we need to disallow rebuilds to an image with properties that are incompatible with the current resource consumption.