Known issues and limitations in Planning Analytics

After an upgrade from a previous version, the Planning Analytics service instance remains in a Pending state

Applies to: 5.4 and later

After you upgrade the Planning Analytics service from a previous version, the service instance might remain in a Pending state.

This occurs if the Planning Analytics service instance fails during an upgrade. The service instance might remain in a Pending state because it is waiting for the bss-init job to complete or because the bss pod remained in a Waiting state with a CrashLoopBackOff error.

Workaround

To resolve this issue, run the following commands to delete the bss pod:

OPERAND_NAMESPACE=<operand_namespace>
oc delete pods -l name=bss -n $OPERAND_NAMESPACE

After a network disruption during an upgrade from version 5.2 to 5.3.1, the TM1 database remains in a Stuck state

Applies to: 5.4 and later

If there is a network disruption while you are upgrading from Planning Analytics service from version 5.2, the TM1 database might remain in a Stuck state.

Workaround

To resolve this issue, delete the tm1-daemon pod and restart the TM1 database:

1. From the Planning Analytics service, stop the TM1 database.
2. Delete the tm1-daemon pods.
   1. Run the following command to get a list of all tm1-daemon pods:

      oc get pods -l app=tm1-daemon

   2. Run the following command to delete all tm1-daemon pods:

      oc delete pods -l app=tm1-daemon

3. From the Planning Analytics service, restart the TM1 database.