Envoy: Envoy v1.16.2 release image not pushed to Dockerhub

[sunjayBhatia]

Moving from slack thread: https://envoyproxy.slack.com/archives/C78HA81DH/p1607556532055200

The job failed on the initial backport PR push but passed on a subsequent retry, (raw log here) however it did not push the envoyproxy/envoy image with the v1.16.2 and updated v1.16-latest tags. That pipeline run did build the -dev named images, which leads me to believe the AZP branch/tag name environment variable was not what we expected it to be in the passed run (maybe hard to tell without admin access to the pipeline).

[sunjayBhatia]

@envoyproxy/stable-maintainers

[sunjayBhatia]

@cpakulski

[cpakulski]

I see that image was successfully pushed to https://hub.docker.com/r/envoyproxy/envoy-google-vrp-dev/tags?page=1&ordering=last_updated

[sunjayBhatia]

Yep, the vrp image was pushed, but not the main release https://hub.docker.com/r/envoyproxy/envoy/tags?page=1&ordering=last_updated

[cpakulski]

1.16.2 docker image has been successfully pushed to DockerHub.

[sunjayBhatia]

thanks!

[sunjayBhatia]

closing, tagged image: https://hub.docker.com/layers/envoyproxy/envoy/v1.16.2/images/sha256-996a3118589f52023e99ae5ef77cdc84c936384375fb68a597b655202f4285bc?context=explore