The "stx" script calls helm without specifying which minikube profile to
use, so it ends up using whichever profile was started last.
TESTS
=============================
* Create 2 different build environments
* Make sure "stx-init-env" and "stx control start/stop/status" don't
interfere with each other in different environments
Reviewed: https:/ /review. opendev. org/c/starlingx /tools/ +/873167 /opendev. org/starlingx/ tools/commit/ a1a02a737351576 1c98da01191df11 80e05c29d3
Committed: https:/
Submitter: "Zuul (22348)"
Branch: r/stx.8.0
commit a1a02a737351576 1c98da01191df11 80e05c29d3
Author: Davlet Panech <email address hidden>
Date: Wed Feb 8 12:36:49 2023 -0500
Avoid minikube profile interference
The "stx" script calls helm without specifying which minikube profile to
use, so it ends up using whichever profile was started last.
TESTS ======= ======= ======= =====
===
* Create 2 different build environments
* Make sure "stx-init-env" and "stx control start/stop/status" don't
interfere with each other in different environments
Closes-Bug: 2006622 f374e9e8ce25b88 d6aee7d2b62 3b85f81a4361b02 e8b348eeb8)
Signed-off-by: Davlet Panech <email address hidden>
Change-Id: Ic92d7792f4a1ba
(cherry picked from commit 714bb7cbf677d70