PowerFlex 4.X: SupportAssist connected but telemetry data does not reach AIOps

1) Confirm SupportAssist is connected. Run the following command on any MVM:

kubectl get supportassist -n powerflex -o yaml

Expected output:

state: Connected
statusMessage: SupportAssist configuration updated successfully

2) Access the Dell AIOps website to validate the issue exists - https://aiops.dell.com/.

Go to Admin > Connectivity.
Find the correct system using it is eSWID (or "Software Unique ID" - SWUID), which can be found in the PowerFlex license section of PFMP, or by running the following command on any MVM:

kubectl get license -n powerflex -o yaml

The eSWID (ELMSIOxxxxx) shows Connected, but 'Last Contacted' date is in the past:

Exec into decks-support-store pod: 

x=$(kubectl get pods -n powerflex|grep -i decks-support|awk '{print $1}'); kubectl exec -it -n powerflex $x -- bash

json files initially get placed in these directories (capacity; health; inventory; performance)

ls -ltl /opt/secure/data/telemetry/vxrackflex/SCALEIO/performance

After transfer, all json files should be deleted from these directories (capacity; health; inventory; performance), and placed in the uploaded directory:

ls -ltr /opt/secure/data/telemetry/vxrackflex/uploaded

Impact

AIOps telemetry is not updated with current data.

There is a defect in the Decks code related to cleanup logic and handling many files when supportassist is unavailable for some time and then comes back online.

The path telemetry json files are supposed to take:

1. On decks-support-store pod, telemetry files initially get placed in a subdirectory (capacity; health; inventory; performance) here: /opt/secure/data/telemetry/vxrackflex/SCALEIO
2. After the telemetry files are sent home using SCG, the files are supposed to get placed here: /opt/secure/data/telemetry/vxrackflex/uploaded and deleted from the subdirectory mentioned above

Deregister/re-register of supportassist will fix the issue: PowerFlex 4.6: How to Deregister and Reregister SupportAssist

There will be a code fix released soon.