search

qlik-oss / qlik-cloud-entitlement-analyzer

The Entitlement Analyzer is a Qlik Sense application built for Qlik Cloud, which provides Entitlement usage overview for your Qlik Cloud tenant.
https://github.com/qlik-oss/qlik-cloud-monitoring-apps
MIT License
4 stars 0 forks source link

Error after migrating to 2.3.0 #30

Open jon-lees-sp opened 6 months ago

jon-lees-sp commented 6 months ago

🐛 Bug report

We recently updated our Entitlement Analyzer monitoring app to 2.3.0 in a multi-tenant, parent-child environment and after doing so we receive an error when reloading the parent app. We see this error:

Storing Assignments-9. The following error occurred: Unexpected token: '-', expected one of: ',', ',', 'as', 'from', 'into' The error occurred here: Store Assignments>>>>>>-<<<<<<9 Into lib://Shared Monitoring Apps:Internal_Monitoring_Apps_S3/QlikMetaCollection/CompiledTenants/Monitoring/Entitlement Analyzer/Assignments-9.qvd Data has not been loaded. Please correct the error and try loading again.

Steps to Reproduce

Updated all target/child tenants with Entitlement Analyzer 2.3.0 and also updated the source/parent tenant. All apps reloaded on schedule. When running source/parent tenant, receive the error mentioned.

Expected behavior

Expect the app to reload without errors.

Actual behavior

Error occurred and continues to occur.

Additional context

Prior Entitlement Analyzer version was 2.1.0

I understand that the monitoring apps might not be backward compatible, but I'm also not clear on how to clear out/ignore the old data so I can load the new versions data successfully.

withdave commented 6 months ago

There is likely a bug in the way the parent apps are handling the upgrade logic, meaning they don't force a concatenation on upgrade. For now, you can delete the compiled QVDs (the ones generated in the CompiledTenants folder in S3) and reload it. We'll add a task for fixing that logic in the parent apps.

Let me know how you get on @jon-lees-sp

jon-lees-sp commented 6 months ago

Hi Dave, I've cleared out the CompiledTenants folder in S3 and then triggered another Reload and it still fails with the same error.

danielpilla commented 6 months ago

It is likely then that you may have a child app that is out of date that is preventing the schema from auto-concatenating. Confirm that all of the child apps/parent apps are on the same (latest) version, then, I would flush the entire directory in S3 and the apps will then rebuild themselves.

jon-lees-sp commented 6 months ago

@danielpilla - thank you, should I flush both Tenants and CompiledTenants? It think all child tenants are up to date but I can double check.