Bug 1295620

Summary:	UI submits all template objects to v1 API, regardless of object API version
Product:	OpenShift Container Platform	Reporter:	Yadan Pei <yapei>
Component:	Management Console	Assignee:	Jessica Forrester <jforrest>
Status:	CLOSED NOTABUG	QA Contact:	Yadan Pei <yapei>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.1.0	CC:	aos-bugs, jliggitt, jokerman, mmccomas, wsun
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1261076	Environment:
Last Closed:	2016-01-05 05:12:42 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:	1261076
Bug Blocks:

Description Yadan Pei 2016-01-05 03:02:16 UTC

+++ This bug was initially created as a clone of Bug #1261076 +++

Description of problem:

Cloned from https://github.com/openshift/origin/issues/4410 to add QE test cases.

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


How reproducible:
Always

Steps to Reproduce:
1. Create a template containing v1beta3 object definitions
2. Load the template into the API
3. In the web UI, create from the template

Actual results:
An API error is returned: "Cannot create object... the apiVersion does not match"

Expected results:
Object is created successfully.

Additional info:

--- Additional comment from Jordan Liggitt on 2015-09-08 10:12:39 EDT ---

Fixed in https://github.com/openshift/origin/pull/4545

--- Additional comment from  on 2015-09-09 06:00:41 EDT ---

QE added one test case https://goo.gl/rEc12o 

Tested on devenv_fedora_2304, it works well

Comment 1 Yadan Pei 2016-01-05 03:03:57 UTC

fixed not merged to OSE 3.1.1

openshift v3.1.1.0
kubernetes v1.1.0-origin-1107-g4c8e6f4
etcd 2.1.2

Comment 2 Jordan Liggitt 2016-01-05 04:24:29 UTC

v1beta3 is no longer supported in 3.1
a test case that uses v1beta3 is no longer valid

Comment 3 Yadan Pei 2016-01-05 05:12:42 UTC

thanks and I will close this issue