let me send you some commands

•

kubectl edit deployment -n epinio epinio-server

• search for

TRACE_LEVEL

• increase the value to

20

• save and exit • wait until the epinio server pod is recreated

then try the command again and check the epinio-server pod's logs

you should find more information on what went wrong

I had a look at the logs controller. One way to get a 400 Bad Request is if the app has no workload. And looking at your

epinio app list

output yours doesn't have one. I think that's the issue.

epinio app logs

gives you the logs of the running app (aka the workload). What you want is the staging logs so the command should be

epinio app logs --staging python-pip

and that should work. Of course, in any case, the command deserves a better error message. I will create an issue for this.

here you go: https://github.com/epinio/epinio/issues/1458

feel free to add more information if you want