The language should say 'controller pod' instead. Example output (see the 2nd item in

I lied, it's client-side: <div class="Box-

Moving back to beta3 and closing. <a class="issue-link js-issue-link" data-error-text=

'deis logs' still references the 'workflow pod' about workflow-cli HOT 4 CLOSED

deis commented on August 24, 2024

'deis logs' still references the 'workflow pod'

from workflow-cli.

Comments (4)

bacongobbler commented on August 24, 2024 1

I'm pretty sure this is a server-side error that's returned, but yes we should fix this up. Should be a one-liner.

from workflow-cli.

bacongobbler commented on August 24, 2024 1

I lied, it's client-side:

workflow-cli/controller/models/apps/apps.go

Lines 100 to 109 in 6c176d2

 if err != nil || len(body) < 1 { 

 return "", fmt.Errorf( 

 `There are currently no log messages. Please check the following things: 

 1) Logger and fluentd pods are running. 

 2) If you just installed the logger components via the chart, please make sure you restarted the workflow pod. 

 3) The application is writing logs to the logger component. 

 You can verify that logs are appearing in the logger component by issuing the following command: 

 curl http://<log service ip>:80/logs/%s on a kubernetes host. 

 To get the service ip you can do the following: kubectl get svc deis-logger --namespace=deis`, appID) 

 }

from workflow-cli.

arschles commented on August 24, 2024

Punting to beta4

from workflow-cli.

arschles commented on August 24, 2024

Moving back to beta3 and closing. #43 fixed this

from workflow-cli.

'deis logs' still references the 'workflow pod' about workflow-cli HOT 4 CLOSED

Comments (4)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent

	if err != nil \|\| len(body) < 1 {
	return "", fmt.Errorf(
	`There are currently no log messages. Please check the following things:
	1) Logger and fluentd pods are running.
	2) If you just installed the logger components via the chart, please make sure you restarted the workflow pod.
	3) The application is writing logs to the logger component.
	You can verify that logs are appearing in the logger component by issuing the following command:
	curl http://<log service ip>:80/logs/%s on a kubernetes host.
	To get the service ip you can do the following: kubectl get svc deis-logger --namespace=deis`, appID)
	}