Bug 1497325

Summary:	unable to find api field in struct Container for the json field \"$setElementOrder/env\""
Product:	OpenShift Container Platform	Reporter:	Justin Pierce <jupierce>
Component:	Master	Assignee:	Maciej Szulik <maszulik>
Status:	CLOSED ERRATA	QA Contact:	ge liu <geliu>
Severity:	low	Docs Contact:
Priority:	low
Version:	3.7.0	CC:	aos-bugs, jokerman, jupierce, mmccomas, wsun
Target Milestone:	---
Target Release:	3.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: Strategic merge patch is causing oc apply error. For example : delete an element from an array (eg. env) and then reorder or modify another array (eg. volumeMounts) and try to apply such patch. Consequence: kubectl apply fails with "unable to find api field in struct Container for the json field "$setElementOrder/env" Fix: Update the algorithm so that it continues operation under described condition. Result: oc apply should work without any problems.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-11-28 22:13:46 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 Justin Pierce 2017-09-29 18:56:54 UTC

Description of problem:
unable to find api field in struct Container for the json field \"$setElementOrder/env\"" occurred during a standard upgrade by openshift ansible. 

sdodson believes this was caused by: https://github.com/kubernetes/kubernetes/issues/50040

Version-Release number of selected component (if applicable):
oc v3.7.0-0.126.6
kubernetes v1.7.0+80709908fd
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://172.31.78.254:443
openshift v3.7.0-0.126.6
kubernetes v1.7.0+80709908fd


How reproducible:
Unknown. Did not occur again when trying the same playbook.

Actual results:
Full openshift-ansible output: http://pastebin.test.redhat.com/520706

Comment 1 Michal Fojtik 2017-10-02 08:08:34 UTC

We are picking that fix in https://github.com/openshift/origin/pull/16615 so this should be fixed on the next upgrade. Justin, is this holding off the current upgrade? Eventually we can backport this but I would prefer to wait.

Comment 2 Justin Pierce 2017-10-02 12:42:06 UTC

Michal - Since it has only happened once, I don't consider it a blocker.

Comment 3 Maciej Szulik 2017-10-06 07:56:13 UTC

Since rebase landed I'm moving this on qa.

Comment 4 ge liu 2017-10-12 06:07:04 UTC

Can't reproduce this issue, and close it since the improvement have been done.

Comment 7 errata-xmlrpc 2017-11-28 22:13:46 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/RHSA-2017:3188