containerized undercloud doesn't work with the default containers file

[Alex Schultz]

Running the following:

openstack overcloud container image prepare \
        --namespace docker.io/tripleomaster \
        --tag current-tripleo \
        --tag-from-label rdo_version \
        --push-destination 192.168.24.1:8787 \
        --output-env-file ~/docker_registry.yaml \
        --output-images-file ~/overcloud_containers.yaml
openstack overcloud container image upload --config-file ~/overcloud_containers.yaml

cp /usr/share/python-tripleoclient/undercloud.conf.sample ~/undercloud.conf
sed -i -e "s/#container_images_file =/container_images_file = \/home\/{{ undercloud_user }}\/docker_registry.yaml/" ~/undercloud.conf
openstack undercloud install --use-heat

Fails with:
2018-05-30 16:18:52Z [undercloud.UndercloudServiceChain.ServiceChain]: CREATE_FAILED StackValidationFailed: resources.ServiceChain: Property error: resources[70].properties: Property DockerTripleoUIImage not assigned
2018-05-30 16:18:52Z [undercloud.UndercloudServiceChain]: CREATE_FAILED Resource CREATE failed: StackValidationFailed: resources.ServiceChain: Property error: ServiceChain.resources[70].properties: Property DockerTripleoUIImage not assigned
2018-05-30 16:18:53Z [undercloud.UndercloudServiceChain]: CREATE_FAILED StackValidationFailed: resources.UndercloudServiceChain.resources.ServiceChain: Property error: ServiceChain.resources[70].properties: Property DockerTripleoUIImage not assigned
2018-05-30 16:18:53Z [undercloud]: CREATE_FAILED Resource CREATE failed: StackValidationFailed: resources.UndercloudServiceChain.resources.ServiceChain: Property error: ServiceChain.resources[70].properties: Property DockerTripleoUIImage not assigned
2018-05-30 16:18:53Z [undercloud.UndercloudServiceChain.LoggingConfiguration]: CREATE_COMPLETE state changed
Stack create failed;
 Stack undercloud/128f8e4d-4417-4dcf-8c51-0b5457090bd1 CREATE_FAILED

Exception: Stack create failed;

[Alex Schultz (alex-schultz)]

We've reworked the container prepare logic so this is no longer an issue.