Bug 1609871 - Istio sidecar injection fails for replicasets with resource requests specified
Summary: Istio sidecar injection fails for replicasets with resource requests specified
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Master
Version: 3.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.10.z
Assignee: Stefan Schimanski
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-30 17:06 UTC by Ben Browning
Modified: 2021-12-10 16:49 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-08-31 06:18:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
ReplicaSet to trigger bug (406 bytes, text/plain)
2018-07-30 17:06 UTC, Ben Browning
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2376 0 None None None 2018-08-31 06:18:51 UTC

Description Ben Browning 2018-07-30 17:06:12 UTC
Created attachment 1471596 [details]
ReplicaSet to trigger bug

Description of problem:

Creating a replicaset that contains a resource request (such as https://gist.github.com/bbrowning/839eb7166261f8c1238a6f024981ae17) fails to ever spin up a pod when Istio is also installed and auto sidecar injection enabled for this namespace.

It fails with events like:

Warning FailedCreate 4m (x17 over 6m) replicaset-controller Error
creating: Internal error occurred: Internal error occurred:
reflect.Value.Addr of unaddressable value

https://github.com/kubernetes/kubernetes/pull/64255/files#diff-e057ec5b2ec27b4ba1e1a3915f715262L118 is cited as a potential fix, with its corresponding Kubernetes 1.10 backport at https://github.com/kubernetes/kubernetes/pull/64971

Neither of those fixes have been tested yet.

This issue does not happen with the same replicaset under Kubernetes 1.10.5.


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

OpenShift Origin v3.10.0-rc.0
Istio v0.8


How reproducible:

happens every time


Steps to Reproduce:

For reference, the exact steps I took are listed at https://gist.github.com/bbrowning/b0e8fd32dd75a264062b2bd3bb17526e . More generic steps are listed below.

1. Install Istio 0.8 into an OpenShift Origin 3.10.0-rc.0 cluster, following the steps at https://istio.io/docs/setup/kubernetes/quick-start/#openshift-origin (Ensure Mutating & Validating webhooks are enabled, all the oc adm policy bits, install Istio itself using the istio-demo.yaml file)
2. oc adm policy add-scc-to-user privileged -z default -n default
3. oc label namespace default istio-injection=enabled
4. oc project default
5. Deploy a replicaset such as the one attached, with a resource request specified

Actual results:
The pod for the replicaset never comes up. oc describe rs - you should see the "reflect.Value.Addr of unaddressable value" error


Expected results:
The pod should come up without error.


Additional info:

This blocks being able to install Knative on OpenShift 3.10.

Comment 1 Paul Morie 2018-07-30 17:16:47 UTC
Changed the parameters of the bug a little bit.

Comment 3 Stefan Schimanski 2018-08-06 09:42:57 UTC
The backport https://github.com/openshift/origin/pull/20509 has merged into the 3.10 branch.

Comment 5 Xingxing Xia 2018-08-21 09:06:08 UTC
Verified in openshift v3.10.28. The pod can come up.

Comment 7 errata-xmlrpc 2018-08-31 06:18:10 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/RHBA-2018:2376


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