Currently the release payload images are stored within the /home/core/registry_data.iso (as a backup of the registry backend), and copied to each node storage after the node's first reboot during the installation by the mount-agent-data.sh script, as part of the setup-local-registry.sh (a preliminary step of the start-local-registry service).

This approach has some drawbacks, since it happens during the installation phase post first-reboot, and it is not monitored as part of the normal installation procedure by the Assisted Service (note: for the rendezvous node, anything happening post first-reboot will not be monitored, since the Assisted Service will not be anymore available).

For these reasons, it would be recommended to copy the release data as an additional Assisted Service step, to be addressed after the OS writing step has been completed (this means also removing the current activity from within the aforementioned scripts/services in the appliance repo). The copy happens before the node's first reboot.