Bug 1673799

Summary:	Rebase openstack-kuryr-kubernetes to a895113
Product:	Red Hat OpenStack	Reporter:	Thierry Vignaud <tvignaud>
Component:	openstack-kuryr-kubernetes	Assignee:	Luis Tomas Bolivar <ltomasbo>
Status:	CLOSED ERRATA	QA Contact:	GenadiC <gcheresh>
Severity:	low	Docs Contact:
Priority:	low
Version:	14.0 (Rocky)	CC:	asegurap, itbrown, slinaber
Target Milestone:	z1	Keywords:	Rebase, RevisionTracker, Triaged, ZStream
Target Release:	14.0 (Rocky)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-kuryr-kubernetes-0.5.3-0.20190121111334.a895113.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-18 13:04:09 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:

Description Thierry Vignaud 2019-02-08 07:27:38 UTC

Rebase openstack-kuryr-kubernetes to a895113 to pull in current version

Comment 5 GenadiC 2019-02-11 12:29:44 UTC

How am I supposed to verify this?

Comment 8 Itzik Brown 2019-03-04 09:44:14 UTC

The kuryr controller image doesn't container the specified RPM version:

python2-kuryr-kubernetes-0.5.1-0.20181010095303.84ad28e.el7ost.noarch
openstack-kuryr-kubernetes-controller-0.5.1-0.20181010095303.84ad28e.el7ost.noarch
python2-kuryr-lib-0.8.1-0.20180907214555.e2beba9.el7ost.noarch
openstack-kuryr-kubernetes-common-0.5.1-0.20181010095303.84ad28e.el7ost.noarch

Comment 9 Itzik Brown 2019-03-06 15:58:52 UTC

Kuryr controller has the following:
    python2-kuryr-kubernetes-0.5.3-0.20190121111334.a895113.el7ost.noarch
    openstack-kuryr-kubernetes-controller-0.5.3-0.20190121111334.a895113.el7ost.noarch
    python2-kuryr-lib-0.8.1-0.20180907214555.e2beba9.el7ost.noarch
    openstack-kuryr-kubernetes-common-0.5.3-0.20190121111334.a895113.el7ost.noarch

Comment 11 errata-xmlrpc 2019-03-18 13:04:09 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-2019:0591