Bug 1983788 - Kubelet may start running before CRI-O
Summary: Kubelet may start running before CRI-O
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.9.0
Assignee: Peter Hunt
QA Contact: Sunil Choudhary
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-19 19:10 UTC by Peter Hunt
Modified: 2021-10-18 17:40 UTC (History)
1 user (show)

Fixed In Version: cri-o-1.22.0-8.rhaos4.9.git1cf63c7
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-18 17:39:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:3759 0 None None None 2021-10-18 17:40:15 UTC

Description Peter Hunt 2021-07-19 19:10:17 UTC
Description of problem:
There is no ordering declared in the CRI-O service file, so they may end up out of order

Version-Release number of selected component (if applicable):
4.6-4.9 are affected

How reproducible:
100%

Steps to Reproduce:
1. cat /usr/lib/systemd/system/crio.service

Actual results:
Should see `Before: kubelet.service`

Expected results:
we do not see this 

Additional info:
there are some weird ordering problems that sometimes arise. upstream issue here https://github.com/cri-o/cri-o/issues/4437

Comment 1 Peter Hunt 2021-07-19 19:43:38 UTC
this occurs because the downstream rpm overwrites the upstream systemd file. The attached version is changed to use the upstream version. version 4.6-4.8 are also fixed (by adding the Before clause, not using the upstream version, to be safe).

Comment 6 errata-xmlrpc 2021-10-18 17:39:54 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.9.0 bug fix and 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.

https://access.redhat.com/errata/RHSA-2021:3759


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