PowerScale InsightIQ 5.x and 6.x shows last Update Timestamp as 2020 or 2021 after import from 4.x

This is due to a system_workload table in the database that is no longer updated or used since 2020 or 2021. This is only be seen on older imported datastores. 

Fix the system_workload 2020 Data Retrieval Delay issue.

IIQ 5.x steps:

Check to see where the database is being stored: 

# kubectl get pvc -A | grep storage

Go to the correct section based on the type of storage:

Local Storage:

# kubectl get pods -A | grep ha-cmo 
 # kubectl exec -it postgres-ha-cmo1-xxxx-x -n atlantic -- psql 
 # \l
 # \c clustername_guid   <<<< get the clustername_guid from \l above for the cluster in question >>>>>>
 # SELECT api, time FROM data_time WHERE resolution = 5 AND api NOT LIKE 'cluster_%%%%' order by time;
 # delete from data_time where api='system_workload';
 # SELECT api, time FROM data_time WHERE resolution = 5 AND api NOT LIKE 'cluster_%%%%' order by time;
 # \q

Refresh the screen after about 5-10 minutes and verify that the date is normal. If the date is not normal, recheck the tables to verify system_workload did not re-create:

# kubectl exec -it postgres-ha-cmo1-xxxx-x -n atlantic -- psql 
 # \l
 # \c clustername_guid   <<<< get the clustername_guid from \l above for the cluster in question >>>>>>
 # SELECT api, time FROM data_time WHERE resolution = 5 AND api NOT LIKE 'cluster_%%%%' order by time;

Network File System (NFS) Storage:

# kubectl get pods -A | grep iiqsm  
 # kubectl exec -it iiqsm-psql-XXXX-xxxx -n atlantic -- psql -U iiqsm -h localhost -d postgres
 # \l
 # \c clustername_guid  <<<< get the clustername_guid from \l above for the cluster in question >>>>>>
 # SELECT api, time FROM data_time WHERE resolution = 5 AND api NOT LIKE 'cluster_%%%%' order by time;
 # delete from data_time where api='system_workload';
 # SELECT api, time FROM data_time WHERE resolution = 5 AND api NOT LIKE 'cluster_%%%%' order by time;
 # \q

Refresh the screen after about 5-10 minutes and verify that the date is normal. If the date is not normal, recheck the tables to verify system_workload did not re-create.

# kubectl exec -it iiqsm-psql-XXXX-xxxxx -n atlantic -- psql -U iiqsm -h localhost -d postgres
 # \l
 # \c clustername_guid  <<<< clustername_guid from \l above >>>>>>
 # SELECT api, time FROM data_time WHERE resolution = 5 AND api NOT LIKE 'cluster_%%%%' order by time;

IIQ 6.x steps:

# sudo docker exec -it iiq-postgres psql -U iiqsm -d insightiq
# \l
# \c <clustername_guid obtained from \l for the cluster in question>
# SELECT api, time FROM data_time WHERE resolution = 5 AND api NOT LIKE 'cluster_%%%%' order by time;
# delete from data_time where api='system_workload';
# SELECT api, time FROM data_time WHERE resolution = 5 AND api NOT LIKE 'cluster_%%%%' order by time;
# \q

Refresh the screen after about 5-10 minutes and verify that the date is normal. If the date is not normal, recheck the tables and verify system_workload did not re-create.

# sudo docker exec -it iiq-postgres psql -U iiqsm -d insightiq
# \l
# \c <clustername_guid obtained from \l for the cluster in question>
# SELECT api, time FROM data_time WHERE resolution = 5 AND api NOT LIKE 'cluster_%%%%' order by time;
# \q