Bug 1853705
Summary: | Deployment Config overview shows 'e is undefined' exception when new pod is starting up | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Jakub Schwan <jschwan> | ||||||
Component: | Management Console | Assignee: | ralpert | ||||||
Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 4.5 | CC: | aos-bugs, jhadvig, jokerman, spadgett, yapei | ||||||
Target Milestone: | --- | ||||||||
Target Release: | 4.6.0 | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: |
Cause: The cause was lack of handling for the 0 case.
Consequence: This caused an error.
Fix: 0 case handling was added.
Result: The bug is fixed.
|
Story Points: | --- | ||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2020-10-27 16:12:04 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Bug Depends On: | |||||||||
Bug Blocks: | 1857821 | ||||||||
Attachments: |
|
Created attachment 1699859 [details] Record of reproducer 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): OpenShift Version 4.5.0-rc.6 Kubernetes Version v1.18.3+6025c28 How reproducible: 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) Actual results: 'e is undefined' exception is thrown Expected results: no exception Additional info: