Created attachment 1687989 [details] the crashing logs page Description of problem: When a pod is Pending and no container is running pod->pod dtails->log is crashing Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create a pod with bad image 2. what for it to become "pending" 3. browse to "pod->pod dtails->log" for that pod. Actual results: Oh no! Something went wrong. Expected results: Empty logs page Additional info:
Actively working this bug, but will most likely continue into upcoming sprint.
yzamir - can you please provide a "bad image" that I can use to test this. Thanks.
> can you please provide a "bad image" that I can use to test this. Thanks. This is a Pod YAML that can create this issue: apiVersion: v1 kind: Pod metadata: name: example labels: app: hello-openshift spec: nodeSelector: disktype: none-existing-node containers: - name: hello-openshift image: openshift/hello-openshift ports: - containerPort: 8080
Created attachment 1698733 [details] Log page for failing pod
yzamir - Can you see if this is still failing? I can not reproduce on the current build. See attached image. version 4.6.0-0.ci-2020-06-23-063142
> Can you see if this is still failing? +1 No, fixed for me on master too, ok to move to qe from my side
Created attachment 1699092 [details] Logs tab loading successfully for Pending pod 1. Create a pod using the YAML in comment 3 2. Visit Logs tab for the Pending pod, the Logs tab is opened successfully and no crash Verified on 4.6.0-0.nightly-2020-06-26-035408
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196