Previously when creating from templates in the web console, the creation would fail if the template contained certain API object types, including persistent volume claims, secrets, and service accounts. This was due to the web console missing these types from its API type map. The type map has now been updated to include these missing types, and the web console also now gracefully handles unrecognized object types, reporting a relevant error message.
Description of problem:
You cannot use a template that references several different types in the Web Console. Examples include persistent volume claims, secrets, service accounts, and many others.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Load a template that uses persistent volume claims, like examples/db-templates/postgresql-persistent-template.json
2. Try to create using the template in the Web Console
The creation fails with no error message.
The creation succeeds.
We should also fail gracefully when templates reference unrecognized types. (To test, change the kind of an object in a template to an invalid value.)
Fix merged in origin:
Test on ose puddle 2015-07-21.3.
$ oc version
Steps to verify:
1.Create template in project "prozyp".
$ oc create -f origin/examples/db-templates/postgresql-persistent-template.json -n prozyp
2.Login web console, create using template postgresql-persistent in project "prozyp".
3.Create template in project "prozyp1". Edit the template, and chage the kind "PersistentVolumeClaim" to an invalid type "TestPersistentVolumeClaim".
$ oc create -f origin/examples/db-templates/postgresql-persistent-template.json -n prozyp1
$ oc edit templates/postgresql-persistent -n prozyp1
4.Login web console, create using template postgresql-persistent in project "prozyp1".
2.Show successful creation info on Overview page.
4.Show failure info, and in details there is error info: Cannot create object. Unrecognized type: TestPersistentVolumeClaim.
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.