Bug 1552613
Summary: | Failed to start pods consuming Config Maps as volumes at OCP 3.4.1.44.38 | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | hgomes |
Component: | Storage | Assignee: | Jan Safranek <jsafrane> |
Status: | CLOSED ERRATA | QA Contact: | Wenqi He <wehe> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.4.0 | CC: | aarrichi, aos-bugs, aos-storage-staff, bchilds, eparis, jokerman, mmccomas, vcorrea |
Target Milestone: | --- | ||
Target Release: | 3.4.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-04-30 05:26:47 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
hgomes
2018-03-07 12:44:12 UTC
This is likely due to an interaction between the redis.conf using subPath https://github.com/3scale/3scale-amp-openshift-templates/blob/master/amp/amp.yml#L333 and this commit which was backported to 3.4 https://github.com/openshift/origin/pull/13895 to fix this bz https://bugzilla.redhat.com/show_bug.cgi?id=1445526 Paul, could you take a look? The template seems weird though. volumeMounts: - name: redis-config mountPath: /etc/redis.conf subPath: redis.conf volumes: ... - name: redis-config configMap: name: redis-config items: - key: redis.conf path: redis.conf It could be an issue with the template that this fix just exposed. It seems like a hack to mount a file into /etc without mounting over the top of /etc. I do agree that https://github.com/kubernetes/kubernetes/pull/45623 should fix Tested on below version: openshift v3.4.1.44.53 kubernetes v1.4.0+776c994 From Jan's comment #8, Pod is running well # oc get pods testpod 1/1 Running 0 8s # oc describe pods Name: testpod Namespace: default Security Policy: anyuid Node: ip-172-18-9-99.ec2.internal/172 Start Time: Mon, 16 Apr 2018 23:33:18 -0400 Labels: <none> Status: Running IP: 10.128.0.14 Controllers: <none> Containers: backend-redis: Container ID: docker://f5c48290466c8966257cf13101304a03db3f337552c2a25ca50aa68a3fdbf60e Image: busybox Image ID: docker-pullable://docker.io/busybox@sha256:58ac43b2cc92c687a32c8be6278e50a063579655fe3090125dcb2af0ff9e1a64 Port: Command: sh -c cat /etc/redis.conf; sleep 3600 State: Running Started: Mon, 16 Apr 2018 23:33:23 -0400 Ready: True Restart Count: 0 Volume Mounts: /etc/redis.conf from redis-config (rw) /var/run/secrets/kubernetes.io/serviceaccount from default-token-fqd3m (ro) Environment Variables: <none> Conditions: Type Status Initialized True Ready True PodScheduled True Volumes: redis-config: Type: ConfigMap (a volume populated by a ConfigMap) Name: redis-config default-token-fqd3m: Type: Secret (a volume populated by a Secret) SecretName: default-token-fqd3m QoS Class: BestEffort Tolerations: <none> Events: FirstSeen LastSeen Count From SubobjectPath Type Reason Message --------- -------- ----- ---- ------------- -------- ------ ------- 16s 16s 1 {default-scheduler } Normal Scheduled Successfully assigned testpod to ip-172-18-9-99.ec2.internal 15s 15s 1 {kubelet ip-172-18-9-99.ec2.internal} spec.containers{backend-redis} Normal Pullingpulling image "busybox" 11s 11s 1 {kubelet ip-172-18-9-99.ec2.internal} spec.containers{backend-redis} Normal Pulled Successfully pulled image "busybox" 11s 11s 1 {kubelet ip-172-18-9-99.ec2.internal} spec.containers{backend-redis} Normal CreatedCreated container with docker id f5c48290466c; Security:[seccomp=unconfined] 11s 11s 1 {kubelet ip-172-18-9-99.ec2.internal} spec.containers{backend-redis} Normal StartedStarted container with docker id f5c48290466c 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-2018:1237 |