This bug was initially created as a copy of Bug #1853705
I am copying this bug because:
We want to backport the fix to 4.5.z.
Description of problem:
Page for Deployment Config overview showed me 'e is undefined' exception, when I tried to access it, when a new pod was starting up. After some time, when the pod is started and running, Deployment Config is again available.
It's easier to reproducer on Deployment Config with "Recreate" strategy. (To see this issue with Rolling strategy I needed to have an issue in image so pod was failing)
Version-Release number of selected component (if applicable):
Every time, with Deployment Config with Recreate strategy.
Steps to Reproduce:
1.Go to Deployment Config page and select one deployment.
2.Click on Start Rollout button.
3.After few moments the exception is displayed.
Note: It's easier to reproducer on Deployment Config with "Recreate" strategy. (To see this issue with Rolling strategy I needed to have an issue in image so pod was failing)
'e is undefined' exception is thrown
*** Bug 1861116 has been marked as a duplicate of this bug. ***
Tried for several times, this is not reproduced.
Verified on 4.5.0-0.nightly-2020-07-30-020337
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.5.5 bug fix update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.