The symptom was not the same.
In this current failure, No Tiller pods were under running at all. As we know, Tiller is the "daemon" of Helm and actually does the work of installation of "application" helm-charts. So without Tiller pods running, none of helm-charts in packed in stx-openstack wouldn't be installed.
In 1826445, stx-openstack was in the middle of applying (up to 26%).
So, we don't have evidence they were duplicated.
Since both Martin and I couldn't see this issue with VM configs (controller 6 Cores + 30GB RAM).
I would suggest Eli or Gopinath test it once more with increased RAM size.
The symptom was not the same.
In this current failure, No Tiller pods were under running at all. As we know, Tiller is the "daemon" of Helm and actually does the work of installation of "application" helm-charts. So without Tiller pods running, none of helm-charts in packed in stx-openstack wouldn't be installed.
In 1826445, stx-openstack was in the middle of applying (up to 26%).
So, we don't have evidence they were duplicated.
Since both Martin and I couldn't see this issue with VM configs (controller 6 Cores + 30GB RAM).
I would suggest Eli or Gopinath test it once more with increased RAM size.