Qlik Sense On Kubernetes: Creating App Error

[Ivan_Ivanovskiy]

Hi!

We try to launch QS on Linux using QS on Kubernetes installation guide.

https://github.com/ChristofSchwarz/qs_on_Kubernetes/tree/master/vagrantprovision

So we've setup QS on Minikube, added users by Auth0 (IDP).

When we try to create new app, we have the next error ("An error occurred while creating the application. Try again"):

May be someboby faced the same problem?

Thanks,

Ivan.

[korsikov]

Are you solved issue? please share your solution with community

[Vincenzo_Esposito]

You need t perform some debug to grab more informations. You can

1) Open the Web browser console and check for errors

2) tail tle engine pod log on the k8s cluster

[Ivan_Ivanovskiy]

We solved it: We opened  full access for every user at Linux server

But now we have another error with app creating. It appeared after rebooting the server:

{"timestamp":"2019-09-23T13:08:37.630Z","log_type":"System","logseverity":"ERROR","thread_id":880772864,"user_id":"auth0\\auth0|5d88a15ffb3de70d7b7bcacf","tenant_id":"Ts9Po3bQLVBFJTL2QZxERjzq1ymIoZJ3","app_id":"0","message":"CTheServer: CreateAppRest caught extended exception 3001: Invalid file name"}

{"timestamp":"2019-09-23T13:08:37.631Z","log_type":"HttpTraffic","logseverity":"WARN","thread_id":880772864,"user_id":"auth0\\auth0|5d88a15ffb3de70d7b7bcacf","tenant_id":"Ts9Po3bQLVBFJTL2QZxERjzq1ymIoZJ3","session_id":"b891835b-e32a-446a-8da8-bc2a5e400b60","app_id":"dsfdsf","server_id":"a46767a4-ad03-45f1-a2e3-fcf1526d0b26","method":"POST","exception":400,"exception_extra":400,"endpoint":"/v1/apps","path":"/v1/apps","query":"","status_code":400,"process_time":8.011345,"work_time":7.911845,"lock_time":0.006300}

[Vincenzo_Esposito]

It seems a non supported character in the application name. Try to use simple standard ascii characters

[korsikov]

since when did the name "test1" become an unsupported character set? do not laugh at me

[Vincenzo_Esposito]

What is the pod which fails?

[Ivan_Ivanovskiy]

Pod: qliksense-engine-

about invalid characters we tried a lot of names.

[Vincenzo_Esposito]

Are u useing a “ Read/Write many” storage?

EFS for AWS

FileAzure for Azure

[Ivan_Ivanovskiy]

We use local MongoDB base. In any way we will check the settings. May be some problems there.