Closed johnbradley closed 5 years ago
When a k8s job has an error we attempt to record the reason why by reading the associated pod logs. Currently this is always recorded as Unable to read logs. Logs from the k8s watcher container include:
Unable to read logs
ERROR:root:Unable to read logs (404)
It looks like we are trying to read pod logs using the job name: https://github.com/Duke-GCB/lando/blob/18149ac99d15d98770aa1906196783dd33ccc0ff/lando/k8s/watcher.py#L85-L91
When a k8s job has an error we attempt to record the reason why by reading the associated pod logs. Currently this is always recorded as
Unable to read logs. Logs from the k8s watcher container include:It looks like we are trying to read pod logs using the job name: https://github.com/Duke-GCB/lando/blob/18149ac99d15d98770aa1906196783dd33ccc0ff/lando/k8s/watcher.py#L85-L91