UI can't get logs pod not found

[jlewi]

BUG REPORT

What happened:

For one of my steps I click on logs to see the logs and I get

{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods "jlewi-notebook-release-317-9de8-2328127088" not found","reason":"No
tFound","details":{"name":"jlewi-notebook-release-317-9de8-2328127088","kind":"pods"},"code":404}

The pod exist though and can be fetched with

 kubectl logs jlewi-notebook-release-317-9de8-2328127088 main

So the pod name is correct.

It could be an issue with namespaces. The workflow controller is not running in the default namespace.

What you expected to happen:

I expected to see the logs.

How to reproduce it (as minimally and precisely as possible):

Click on logs for any step.

Anything else we need to know?:

Environment:

• Argo version:

argoproj/argoui:v2.1.0-alpha1

• Kubernetes version :

clientVersion:
buildDate: 2017-12-21T06:34:11Z
compiler: gc
gitCommit: 6260bb08c46c31eea6cb538b34a9ceb3e406689c
gitTreeState: clean
gitVersion: v1.8.6
goVersion: go1.8.3
major: "1"
minor: "8"
platform: linux/amd64
serverVersion:
buildDate: 2018-01-31T21:39:04Z
compiler: gc
gitCommit: 192ccad06d24af9828cbf42330e1d915cb586406
gitTreeState: clean
gitVersion: v1.8.7-gke.1
goVersion: go1.8.3b4
major: "1"
minor: 8+
platform: linux/amd64

[bobhenkel]

This issue will also happen with argo log command on the cli. I too have installed argo into a custom namespace, if that ends up being related.

[ankushagarwal]

It could be an issue with namespaces. The workflow controller is not running in the default namespace.

I don't think it's a namespace issue. I tried a vanilla deployment of argo and I am hitting the same issue.

[jessesuen]

@alexmt do you believe this to be fixed in beta2?

[ankushagarwal]

Gentle ping to see if there is any progress on this

[jessesuen]

I just reproduced this and this is not fixed in beta2. It appears that for the logs, UI does not include namespace in its query.

[mthx]

Having upgraded to 2.1-beta2 this was proving annoying. Possible fix on argoproj/argo-ui#3

[alexmt]

Your change does fix issue @mthx . Thank you!