CRs and limitations

Problems and limitations are identified with a change request (QCCR) number. For more information about known problems, visit softwaresupport.hpe.com, or contact your HPE Support representative directly.

Limitations

• When clicking the “Back” button during the Suite installation, the parameter values entered for the capabilities are lost.
• The suite reconfiguration has not been implemented yet.
• During the Suite installation, in-line validation of the entered values is not yet available – values are validated once the user clicks “Next”.
• The users are not yet forced to change their password after the first login.
• When installing both OMi and BVD, the same administrator password must be used for the single sign-on to work.
• No dependency between the management packs has been implemented yet.

Open CRs and workarounds

Title: Reboot does not work. Pods are in status CrashLoopBackOff. (QCCR8B27564)

Description: This is related to the vault-renewal container, which does not get a valid token. You have to delete the failed pods. Once the pods are deleted, they are recreated automatically and should run without error.

Workaround: You can get the status of all pods with the following command:

kubectl get pods --all-namespaces

First delete all failed database related pods (suite-db, idm-postgresql, postgresql-aplm). Next, delete all failed pods within the namespace core. After that delete all failed pods within the namespace opsbridge, starting with postgres, ucmdb, omi, redis, bvd, obr-server, obr-rc).

Use the following command to delete the failed pods within the namespaces specified above:

kubectl delete pod <pod_name> --namespace <pod_namespace>

---

Title: Kafka topics not getting created as Kafka pod keeps restarting after PE Containers deployment. (QCCR1A190723)

Description: This issue occurs when PE Kafka and PE admintools pods are already up and running and PE Zookeeper takes a longer time to come up.

Workaround: Execute the following commands on the master node:

1. Get the namespace under which the Performance Engine containers are configured and running:

   dep_namespace=$(kubectl get pods -l app=hpe-opsb-pe-admintools-pod --all-namespaces | tail -n 1 | awk '{print $1}')

2. Get the pod admintools pod name:

   admintool_pod=$(kubectl get pods -l app=hpe-opsb-pe-admintools-pod --all-namespaces | tail -n 1 | awk '{print $2}')

3. Reconfigure the password for redis:

   kubectl exec -it $admintool_pod --namespace=$dep_namespace -- bash admintools -c

4. Reconfigure the password for Vertica as well:

   kubectl exec -it $admintool_pod --namespace=$dep_namespace -- bash admintools -cdb

---