CRI-O v1.18.3

The release notes have been generated for the commit range v1.18.2…afe1821 on Tue, 20 Oct 2020 21:50:35 UTC.

Downloads

Download the static release bundle via our Google Cloud Bucket: crio-afe1821d5.tar.gz

Fixed regression where it was not able to run exec any more when compiling CRI-O with newer go versions (#4192, @saschagrunert)
Fix a bug where a sudden reboot causes incomplete image writes. This could cause image storage to be corrupted, resulting in an error layer not known. (#3972, @giuseppe)
Fixed a bug where a container creation failure caused that container to leak in the runtime (#4237, @haircommander)
Fixed bug where pod names would sometimes leak on creation, causing the kubelet to fail to recreate (#3950, @haircommander)
If conmon is v2.0.19 or greater, ExecSync requests will not double fork, causing systemd to have fewer conmons re-parented to it (#3912, @haircommander)

Fixed a bug where exec sync requests (manually or automatically triggered via readiness/liveness probes) overwrite the runtime info.runtimeSpec.process.args of the container status (for example via crictl inspect). (#3992, @openshift-cherrypick-robot)
Fix bug where empty config fields having to do with storage cause /info requests to return incorrect information (which causes cadvisor to fail to read imageFs information) (#4176, @openshift-cherrypick-robot)
Fixed crio restart behavior to make sure that Pod creation timestamps are restored and the order in the list of pods stays stable across restarts (#4010, @openshift-cherrypick-robot)