Bug 1751125 - [Kuryr] Kuryr controller should have the label name=kuryr-controller
Summary: [Kuryr] Kuryr controller should have the label name=kuryr-controller
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.11.z
Assignee: Luis Tomas Bolivar
QA Contact: Itzik Brown
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-11 08:57 UTC by Itzik Brown
Modified: 2019-10-18 01:34 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-18 01:34:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift openshift-ansible pull 11924 0 None closed Kuryr controller label 2020-09-17 06:05:03 UTC
Red Hat Product Errata RHBA-2019:3139 0 None None None 2019-10-18 01:34:58 UTC

Description Itzik Brown 2019-09-11 08:57:52 UTC 
Description of problem:
It seems that in upstream the Kuryr controller pods have the label name=kuryr-controller. We should use the same in our official release. The lack of this label cause our port pool tests to fail because the tests relies on looking the controller tests based on this label.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Itzik Brown 2019-10-06 13:29:11 UTC 
openshift-ansible-3.11.147-1.git.0.bd6c010.el7.noarch
Comment 3 errata-xmlrpc 2019-10-18 01:34:36 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:3139
Note You need to log in before you can comment on or make changes to this bug.