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

Bug 1854200

Summary:	Default hooks dir is wrong and the needed (/etc/containers/oci/hooks.d/) was removed
Product:	OpenShift Container Platform	Reporter:	OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component:	Node	Assignee:	Peter Hunt <pehunt>
Status:	CLOSED ERRATA	QA Contact:	MinLi <minmli>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	4.5	CC:	aos-bugs, jhou, jokerman, mifiedle, mpatel, pehunt, rphillips, umohnani, wabouham
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-13 17:44:51 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:
Bug Depends On:	1853735
Bug Blocks:	1847805

Comment 1 Peter Hunt 2020-07-06 19:32:55 UTC

note: this regression was introduced early in the 4.5 timeframe, and was not backported to 4.4.

Comment 4 MinLi 2020-07-07 04:21:56 UTC

verified in version: 4.5.0-0.nightly-2020-07-06-211538 

$ oc get mc 01-master-container-runtime -o yaml | grep  crio
path: /etc/crio/crio.conf.d/00-default

$ oc get mc 01-worker-container-runtime -o yaml | grep crio
path: /etc/crio/crio.conf.d/00-default

$ oc debug node/ip-10-0-149-109.us-east-2.compute.internal
Starting pod/ip-10-0-149-109us-east-2computeinternal-debug ...
To use host binaries, run `chroot /host`
Pod IP: 10.0.149.109
If you don't see a command prompt, try pressing enter.
sh-4.2# chroot /host 
sh-4.4# cat /etc/crio/crio.conf.d/00-default | grep -i hook
hooks_dir = [
    "/etc/containers/oci/hooks.d",
sh-4.4#

Comment 5 errata-xmlrpc 2020-07-13 17:44:51 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-2020:2409