Enable content trust in admiral does not work if you have whitelist enabled already

[mhagen-vmware]

If you install a VCH with a whiltelist enabled already (docker hub):

./vic-machine-linux create --no-tlsverify --target x.x.x.x --user administrator@vsphere.local --password xxx --name default-vch --public-network /ha-datacenter/network/vm-network --bridge-network /ha-datacenter/network/bridge --compute-resource /ha-datacenter/host/cls/Resources --image-store datastore1 --thumbprint BA:22:27:2E:AC:B1:5A:52:DC:0F:07:DF:37:70:21:69:8F:2D:89:F0 --registry-ca ca.crt --whitelist-registry registry.hub.docker.com

Then enable content trust within admiral, the whitelist will not be changed and you can never add harbor as a whitelisted registry:

Sep  8 2017 19:17:41.117Z WARN  error getting config from source: config not modified
Sep  8 2017 19:17:41.117Z ERROR error updating config: whitelist merge allows entries that are not in the original whitelist

[stuclem]

Attempted release note:

---

• Enabling content trust in Management Portal does not work if a VCH is in whitelist mode. #6258
  If you install a VCH with whiltelist mode enabled, attempting to a enable content trust on a vSphere Integrated Containers Registry in Management Portal does not update the whitelist, and you cannot pull from that registry.

---

@mhagen-vmware is this OK?

[mhagen-vmware]

LGTM

[stuclem]

Thanks @mhagen-vmware