LI83221: ANALYTICS SUBSYSTEM FAILS TO UPGRADE WHEN INTERNAL STORAGE HAS BEEN DISABLED

APAR status

• Closed as program error.

Error description

• The upgrade of the analytics subsystem to version 10.0.8.0 never
  completes if analytics has been configured for offload only
  (internal storage has been disabled).
  

Local fix

• Users should be able to work around the problem by temporarily
  enabling internal storage. To enable temporary storage take the
  following steps:
  
  * Update the Top Level CR (TLCR) to include the following:
  spec:  analytics:
     storage:
       enabled: true
  * Once this change has been saved, the analytics storage pods
  should start and the upgrade should continue.
  * After the upgrade to v10.0.8.0 has completed (analytics is
  showing as 'Ready' with reconciled version = 10.0.8.0), storage
  can be disabled again by setting the 'enabled' value given above
  to 'false'.
  
  * The customer can then delete the storage PVCs that have been
  created when the storage pods started.
  

Problem summary

• When upgrading to API Connect version 10.0.8.0 from an existing
  deployment that includes analytics with internal storage
  disabled, the upgrade will never complete.
  
  When viewing the status of the Kubernetes resources, after the
  version of the AnalyticsCluster instance has been set to
  '10.0.8.0', the status will change to 'Pending', but will never
  return to 'Running'.
  
  The API Connect operator logs include the following messages:
  
  "unable to obtain a7s client to delete obsolete backup
  repository"
  "analytics service endpoint was not found for service: storage"
  

Problem conclusion

• It is possible to force the upgrade to continue by temporarily
  enabling analytics internal storage. Please refer to the
  following documentation, but set 'storage.enabled' to 'true':
  
  https://www.ibm.com/docs/en/api-connect/10.0.8?topic=options-dis
  able-local-storage
  
  Once the upgrade has completed, internal storage can be disabled
  again using the same process. Please note that new PVC(s) will
  have been created when storage was enabled. After re-disabling
  internal storage, these PVCs can be manually removed using:
  
  kubectl delete pvc <pvc_name> -n <namespace>
  
  where <pvc_name> has the following naming pattern:
  
  data-analytics-storage
  
  A fix is targeted for API Connect version 10.0.8.1.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  API CONNECT ENT

• Fixed component ID

  5725Z2201

Applicable component levels