Bug 1497325 - unable to find api field in struct Container for the json field \"$setElementOrder/env\""
Summary: unable to find api field in struct Container for the json field \"$setElement...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Master
Version: 3.7.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 3.7.0
Assignee: Maciej Szulik
QA Contact: ge liu
Depends On:
TreeView+ depends on / blocked
Reported: 2017-09-29 18:56 UTC by Justin Pierce
Modified: 2017-11-28 22:13 UTC (History)
5 users (show)

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.
Clone Of:
Last Closed: 2017-11-28 22:13:46 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:3188 0 normal SHIPPED_LIVE Moderate: Red Hat OpenShift Container Platform 3.7 security, bug, and enhancement update 2017-11-29 02:34:54 UTC

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

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.


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