Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1983788

Summary:	Kubelet may start running before CRI-O
Product:	OpenShift Container Platform	Reporter:	Peter Hunt <pehunt>
Component:	Node	Assignee:	Peter Hunt <pehunt>
Node sub component:	CRI-O	QA Contact:	Sunil Choudhary <schoudha>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	aos-bugs
Version:	4.7
Target Milestone:	---
Target Release:	4.9.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	cri-o-1.22.0-8.rhaos4.9.git1cf63c7	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-10-18 17:39:54 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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