Images with visibility set to "community" will fail to replicate to multiple availability zones

Products

• VMware Integrated OpenStack

Issue/Introduction

Symptoms:
An instance is failing to launch from an image in any availability zone except the first when the image availability is set to "community".

Environment

7.x

Cause

Image visibility is limited when it is marked as "community". This is by design as community images can only be listed if the image is subscribed to directly.  The glance_vmw_replicator service that is responsible for copying the corresponding Virtual Machine Template across vCenters utilizes a service account. The service account being utilized has no subscription to images nor the opportunity to.  This results in the community image never being seen by the service account, and the corresponding Virtual Machine Template is never copied across vCenters.

Resolution

Workaround:
To resolve this set the image visibility to "public". Ensure the Virtual Machine Template is copied over to each vCenter by checking within the vSphere web client. Once the template is copied over we can change the visibility back to community.