Bug 1731366 - Could not create app from template on console
Summary: Could not create app from template on console
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Templates
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.2.0
Assignee: Adam Kaplan
QA Contact: XiuJuan Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-19 09:22 UTC by shahan
Modified: 2019-10-16 06:30 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:30:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:30:17 UTC

Description shahan 2019-07-19 09:22:08 UTC
Description of problem:
Could not create app from template on console, the templateinstance failed.

Version-Release number of selected component (if applicable):

4.2.0-0.nightly-2019-07-19-030142

How reproducible:
Always

Steps to Reproduce:
1. oc new-app --template=amq63-ssl --param=AMQ_TRUSTSTORE_PASSWORD=123 --param=AMQ_KEYSTORE_PASSWORD=123 -n hasha-pro1

2. Goto Developer console, add from Browse Catalog, select template named
JBoss A-MQ 6.3 (Ephemeral with SSL), instantiate template

3. $ oc describe templateinstance amq63-ssl-hrz4s -n hasha-pro1

Actual results:
1. the app created sucessfully
2. It will fail with InstantiateFailure
3.  Message:	 no kind is registered for the type v1.Template in scheme
        "k8s.io/kubernetes/pkg/api/legacyscheme/scheme.go:29"

Expected results:
Should create successfully as cli

Additional info:

Comment 1 Samuel Padgett 2019-07-19 09:29:19 UTC
Changing component to Templates since we're using the TemplateInstance API and not creating the resources directly. The oc command is not exactly equivalent since it doens't use TemplateInstances.

Note that the legacy OpenShift APIs with no group have been removed since 4.1. We might need to update the template itself.

Comment 2 shahan 2019-07-19 09:51:02 UTC
OK, one question here why we use two totally different ways to do it? Thanks

Comment 3 shahan 2019-07-19 10:23:24 UTC
BTW, it just worked against previous 4.2 nightly build on console, such as 4.2.0-0.nightly-2019-07-18-120653.

Comment 4 Ben Parees 2019-07-30 14:46:33 UTC
There were some openshift api server resource issues introduced in that build. They have been resolved and this appear to be working now.  Setting to QA.

Comment 5 XiuJuan Wang 2019-07-31 02:03:04 UTC
Can't reproduce this issue against 4.2.0-0.nightly-2019-07-28-222114 .

Comment 6 errata-xmlrpc 2019-10-16 06:30:08 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:2922


Note You need to log in before you can comment on or make changes to this bug.