Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1733806

Summary: Template with resource `spec.template` can cause runtime error when created in console
Product: OpenShift Container Platform Reporter: Samuel Padgett <spadgett>
Component: Management ConsoleAssignee: Samuel Padgett <spadgett>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.11.0CC: aos-bugs, hasha, jokerman
Target Milestone: ---   
Target Release: 3.11.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
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.
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-13 14:09:21 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:

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