Old version of containers in LAYERED 20200702T163103Z helm-chart

[Nicolae Jascanu]

Brief Description
-----------------
The helm-chart of the last LAYERED image is using an old version of containers: 20200505T204039Z instead of 20200701T054008Z

http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200702T163103Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz

Severity
--------
Critical: for Ussuri upgrade

Steps to Reproduce
------------------
Check the stx-openstack.yaml from helm-charts-stx-openstack-centos-stable-versioned.tgz

Expected Behavior
------------------
The expected version should be the same as the one from MONOLITHIC: 20200701T054008Z: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200702T080012Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz

Test Activity
-------------
Sanity

[Frank Miller (sensfan22)]

The latest builds as of July 7 are now using the correct helm charts. This is no longer an issue for the current builds.

[Scott Little (slittle1)]

I've found that the problem has already been at least partially fixed.

During ussuri debugging a week or so ago it was found that the flock layered build had been switched to use a non-layered version of the helm chart sub-task. I never did find out how that happened, but it was switched back, and that has corrected several problems. I suspect it was a misguided attempt to pick up monolithic built docker images.

The helm charts currently being produced are not simply identical to those of the monolithic build on two fronts.

1) The helm charts now point to the docker images produced by the container layer build, which are temporarily published via the slittlewrs rather than starlingx dockerhub user/org.

2) Flock layer builds before container layer, so the helm charts point to the previous containers build. They currently are not updates when the container layer completes it's build. Nor does the containers layer build it's own helm charts. So layered built helm charts are a day behind the monolithic built ones until this is corrected.

Issue 2 needs a fix.

Issue 1, I'd like to leave as is for the moment, and ask that you test this configuration to determine if the layer build is producing good containers.

[Frank Miller (sensfan22)]

Based on Scott's update, the issue is partially fixed and issue #2 is the remaining issue. Re-tagging this to stx.5.0 as the workaround for stx.4.0 is to ensure at least one ISO build is triggered after the final docker image build. As docker builds are scheduled once per week and ISO builds are daily this is acceptable for stx.4.0.