Angie Wang 5e61519ac9 Solve the stx-openstack reapply issue on controller-1 ... After stx-openstack applied, the stx-openstack reapply shouldn't trigger the charts reinstallation if there has no overrides changed for charts. However, the reinstallation happens after swacting active controller to controller-1 due to the generated images overrides on controller-1 are different from before. The images overrides generation requires walking through the stx-openstack charts stored under /scratch, but charts do not exist on controller-1's /scratch as it's an unreplicated filesystem. This causes the images overrides to differ between controller-1 and controller-0. This commit updates to walk through charts and get the images for charts during application-upload, then save the images list for each chart into the existing images file under aramda directory /opt/platform/armada. The images file would be used for retrieving the images for charts to generate images overrides. Closes-Bug: 1816173 Change-Id: I4f00c3031decb063f8f126d0c837acd4dde56fc3 Signed-off-by: Angie Wang <angie.wang@windriver.com> (cherry picked from commit cb4b30bf56)		2019-02-25 15:23:33 +00:00
..
build_srpm.data	Solve the stx-openstack reapply issue on controller-1	2019-02-25 15:23:33 +00:00
sysinv.spec	Replace compiled crushmaps with human readable versions	2019-01-18 09:27:02 +00:00