1430555 – OpenShift Container Platform March Image Refresh

Bug 1430555 - OpenShift Container Platform March Image Refresh

Summary: OpenShift Container Platform March Image Refresh

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	ImageStreams
Sub Component:
Version:	3.4.1
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	---
Target Release:	3.4.z
Assignee:	Samuel Munilla
QA Contact:	Dongbo Yan
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:	1432508 1454886 1460799 1461601 1482521
TreeView+	depends on / blocked

Reported:	2017-03-08 23:47 UTC by Troy Dawson
Modified:	2017-09-13 17:53 UTC (History)
CC List:	3 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:	Because the openshift images are layered, an image refresh picks up all the security and bug fixes of the lower layers. This image refresh fixes several security and normal bugs.
Clone Of:
Clones:	1432508 (view as bug list)
Environment:
Last Closed:	2017-03-15 20:27:23 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2017:0513	0	normal	SHIPPED_LIVE	OpenShift Container Platform 3.4.1.10, 3.3.1.17, and 3.2.1.28 images update	2017-03-16 04:16:45 UTC

Description Troy Dawson 2017-03-08 23:47:38 UTC

Refresh OCP 3.2, 3.3, and 3.4 images.

openshift3/ose:v3.2.1.28-2
openshift3/openvswitch:v3.2.1.28-2
openshift3/ose-deployer:v3.2.1.28-2
openshift3/ose-docker-builder:v3.2.1.28-2
openshift3/ose-docker-registry:v3.2.1.28-2
openshift3/ose-f5-router:v3.2.1.28-2
openshift3/ose-haproxy-router:v3.2.1.28-2
openshift3/ose-keepalived-ipfailover:v3.2.1.28-2
openshift3/ose-pod:v3.2.1.28-2
openshift3/ose-recycler:v3.2.1.28-2
openshift3/ose-sti-builder:v3.2.1.28-2
openshift3/logging-auth-proxy:3.2.1-9
openshift3/logging-deployment:3.2.1-9
openshift3/logging-elasticsearch:3.2.1-11
openshift3/logging-fluentd:3.2.1-7
openshift3/logging-kibana:3.2.1-7
openshift3/metrics-cassandra:3.2.1-8
openshift3/metrics-deployer:3.2.1-5
openshift3/metrics-hawkular-metrics:3.2.1-6
openshift3/metrics-heapster:3.2.1-7
openshift3/node:v3.2.1.28-2

openshift3/ose:v3.3.1.17-2
openshift3/openvswitch:v3.3.1.17-2
openshift3/ose-deployer:v3.3.1.17-2
openshift3/ose-docker-builder:v3.3.1.17-2
openshift3/ose-docker-registry:v3.3.1.17-2
openshift3/ose-egress-router:v3.3.1.17-2
openshift3/ose-f5-router:v3.3.1.17-2
openshift3/ose-haproxy-router:v3.3.1.17-2
openshift3/ose-keepalived-ipfailover:v3.3.1.17-2
openshift3/ose-pod:v3.3.1.17-2
openshift3/ose-recycler:v3.3.1.17-2
openshift3/ose-sti-builder:v3.3.1.17-2
openshift3/logging-auth-proxy:3.3.1-4
openshift3/logging-curator:3.3.1-4
openshift3/logging-deployer:v3.3.1.17-2
openshift3/logging-elasticsearch:3.3.1-4
openshift3/logging-fluentd:3.3.1-5
openshift3/logging-kibana:3.3.1-4
openshift3/metrics-cassandra:3.3.1-5
openshift3/metrics-deployer:v3.3.1.17-2
openshift3/metrics-hawkular-metrics:3.3.1-5
openshift3/metrics-heapster:3.3.1-5
openshift3/node:v3.3.1.17-2

openshift3/ose:v3.4.1.10-2
openshift3/openvswitch:v3.4.1.10-2
openshift3/ose-deployer:v3.4.1.10-2
openshift3/ose-docker-builder:v3.4.1.10-2
openshift3/ose-docker-registry:v3.4.1.10-2
openshift3/ose-egress-router:v3.4.1.10-2
openshift3/ose-f5-router:v3.4.1.10-2
openshift3/ose-haproxy-router:v3.4.1.10-2
openshift3/ose-keepalived-ipfailover:v3.4.1.10-2
openshift3/ose-pod:v3.4.1.10-2
openshift3/ose-recycler:v3.4.1.10-2
openshift3/ose-sti-builder:v3.4.1.10-2
openshift3/image-inspector:2.1-8
openshift3/logging-auth-proxy:3.4.1-4
openshift3/logging-curator:3.4.1-4
openshift3/logging-deployer:v3.4.1.10-2
openshift3/logging-elasticsearch:3.4.1-6
openshift3/logging-fluentd:3.4.1-4
openshift3/logging-kibana:3.4.1-4
openshift3/metrics-cassandra:3.4.1-5
openshift3/metrics-deployer:v3.4.1.10-2
openshift3/metrics-hawkular-metrics:3.4.1-8
openshift3/metrics-heapster:3.4.1-5
openshift3/node:v3.4.1.10-2

Comment 3 errata-xmlrpc 2017-03-15 20:27:23 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-2017:0513

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