Bug 2034898 - Regression in recently added Events feature
Summary: Regression in recently added Events feature
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: rdobosz
QA Contact: Itzik Brown
Depends On:
TreeView+ depends on / blocked
Reported: 2021-12-22 12:45 UTC by rdobosz
Modified: 2022-03-12 04:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2022-03-12 04:39:45 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift kuryr-kubernetes pull 618 0 None open Bug 2034898: Added missing raise statement for not ready resource. 2021-12-23 15:10:31 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-12 04:40:00 UTC

Description rdobosz 2021-12-22 12:45:37 UTC
Description of problem:

During development of Events in Kuryr-Kubernetes there has been retry triggering missing due to missing statement, resulting in race condition between kuryr and neutron for making port state ACTIVE/DOWN.

How reproducible:

Steps to Reproduce:
1. create a pod
2. look at the timings, when pod would get the running state
3. it might be ready right away, but most of the time it should take a while to make it run.

Actual results:

Expected results:

Additional info:

Comment 5 Itzik Brown 2022-01-06 12:53:04 UTC
Pod creation for the first time takes about 1 minute after the image is downloaded and a project is created.
After that it takes 8 seconds.
Verified with 4.10.0-0.nightly-2022-01-05-181126.

Comment 8 errata-xmlrpc 2022-03-12 04:39:45 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 (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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