Bug 1733806 - Template with resource `spec.template` can cause runtime error when created in console
Summary: Template with resource `spec.template` can cause runtime error when created i...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 3.11.z
Assignee: Samuel Padgett
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-28 19:43 UTC by Samuel Padgett
Modified: 2019-08-13 14:09 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
The web console in rare cases would fail instantiating templates that contained custom resources with a `spec.template` property. The bug has been fixed, and instantiate template now successfully completes with these resources.
Clone Of:
Environment:
Last Closed: 2019-08-13 14:09:21 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin-web-console pull 3140 0 None None None 2019-07-28 19:45:02 UTC
Red Hat Product Errata RHBA-2019:2352 0 None None None 2019-08-13 14:09:24 UTC

Description Samuel Padgett 2019-07-28 19:43:09 UTC 
See discussion in https://github.com/openshift/console/issues/2136. This happens when there is a template resource with `spec.template` but no `spec.template.spec` property.
Comment 1 Samuel Padgett 2019-07-28 19:52:35 UTC 
This is only a problem in the 3.x console.
Comment 3 shahan 2019-08-05 06:33:01 UTC 
Verified this bug. Now the web console can handle template with resource `spec.template` correctly.
OpenShift Master:
v3.11.135
Kubernetes Master:
v1.11.0+d4cacc0
OpenShift Web Console:
v3.11.135
Comment 5 errata-xmlrpc 2019-08-13 14:09:21 UTC 
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, 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-2019:2352
Note You need to log in before you can comment on or make changes to this bug.