Description of problem: Should treat 'resourceVersion 'as an opaque field on web console Version-Release number of selected component (if applicable): OpenShift Master: v3.9.0-0.38.0 Kubernetes Master: v1.9.1+a0ce1bc657 OpenShift Web Console: v3.9.0-0.38.0 How reproducible: Always Steps to Reproduce: 1. $ oc create -f https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/deployment/dc-with-two-containers.yaml 2. $ oc get dc dctest -o yaml > dc-with-two-containers.yaml 3. $ oc delete dc dctest 4.Login to web console and click 'Import YAML / JSON', paste above YAML file and create. 5. oc create -f dc-with-two-containers.yaml via CLI Actual results: 4. Unable to create the deployment config 'dctest'. Reason: resourceVersion should not be set on objects to be created 5. create DC successfully. Expected results: Web Client should be consistent with CLI in terms of ignoring these fields as an opaque, such as 'resourceVersion' 'uid' Additional info:
https://github.com/openshift/origin-web-console/pull/2796
Commits pushed to master at https://github.com/openshift/origin-web-console https://github.com/openshift/origin-web-console/commit/d740e2cc8fe3d410c4821d6b64b363624461a3d2 Bug 1543324 - Strip resourceVersion in import YAML for new resources Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1543324 https://github.com/openshift/origin-web-console/commit/f9699d3316f6d8ef42b4b754e9e4d7d43e0bb530 Merge pull request #2796 from spadgett/import-yaml-resource-version Automatic merge from submit-queue. Bug 1543324 - Strip resourceVersion in import YAML for new resources Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1543324 /kind bug /assign @benjaminapetersen /cc @juanvallejo
Checked on OpenShift Web Console: v3.9.0-0.47.0 resourceVersion now is removed/regarded as opaque field when creating from web console if resoureVersion is included in yaml/json