Symptoms


In same cases there exits a discrepancy between the BSS version deployed and the BSS application showing in UI.

For example, checking with helm we see the latest version installed, in this case bss-21.8-406:

# /usr/local/bin/helm -n <namespace> list
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
bss prod-cbc 4 2022-12-28 19:21:10.820038819 +0000 UTC deployed bss-21.8.406

In this case, the command used to upgrade the componet was:

# setup-product.sh -s helmfile-deploy -n <namespace> -c bss -c oss

But from provider CP we still see one the previous versions installed:


Cause

This happens because helmfile-deploy will upgrade bss-war only if in config.yaml file is set specifically:


components:
  bss:
    version: 21.8.406

This issue has been recognized as a Software issue with id OA-32913.

Resolution

This issue can be work around by following this procedure to update the components:


1. upgrade bss and branding-ui charts with the following command:

# setup-product.sh -n <namespace> -s helmfile-deploy -c bss -c branding-ui-cluster

2. extract the config.yaml file from the secret:

# kubectl get secret helmfile-deploy -n <namespace> -o "jsonpath={.data['config\.yaml']}" | base64 -d > config-test.yaml 

3. write inside the config-test.yaml the bss.version: 21.x.x(installed in p1 version) and save.
4. upgrade oss with the following command:

# setup-product.sh -n <namespace> -f config-test.yaml -c oss