Bug 1711340
Summary: | Kubernetes Pod Template is randomly removed | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Gabe Montero <gmontero> |
Component: | ImageStreams | Assignee: | Gabe Montero <gmontero> |
Status: | CLOSED ERRATA | QA Contact: | XiuJuan Wang <xiuwang> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.1.z | CC: | adam.kaplan, aos-bugs, fshaikh, gmontero, jokerman, mmccomas, pweil, wzheng, xiuwang |
Target Milestone: | --- | ||
Target Release: | 4.2.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: The OpenShift Jenkins Sync plugin confused ImageStreams and ConfigMaps with the same name when processing them for Jenkins k8s plugin PodTemplates
Consequence: An event for one type could delete the pod template created from another type
Fix: The OpenShift Jenkins Sync plugin was modified to keep track of which api object type created the pod template of a given name.
Result: Jenkins k8s plugin PodTemplates created by the OpenShift Sync Plugin's mapping from ConfigMap/ImageStreams are not inadvertently deleted when two types with the same name exist in the cluster.
|
Story Points: | --- |
Clone Of: | 1711334 | Environment: | |
Last Closed: | 2019-10-16 06:28:56 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1709626, 1711334 | ||
Bug Blocks: |
Comment 1
Gabe Montero
2019-05-17 14:27:42 UTC
The created Kubernetes Pod Template using the ConfigMap style will not removed more than a dozen hours. Verified with jenkins image registry.svc.ci.openshift.org/ocp/4.2-2019-05-27-211046@sha256:f2d60cfc24ce881c4def3bc3bc4b1c8ab5fd031508c12b3a6bd85f1dbb52081a(get from 4.2.0-0.ci-2019-05-27-211046 payload) with openshift-sync:1.0.37 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-2019:2922 |