From 21801a11a7c8bf3fbed3e7be82170ef68b36b657 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fabiano=20Fid=C3=AAncio?= Date: Mon, 9 Nov 2020 13:28:36 +0100 Subject: [PATCH] versions: Revert "version: revert back to crio 1.8.3" MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This reverts commit ff13bde3c1bd03b5ed0c93e7ea315befd24a75b7, which moved back CRI-O to v1.18.3. The was, IMHO, a little bit premature. We want to know exactly what are the issues on v1.18.4, solve those, and be prepared for a v1.18.5 bump (or even a bump to a specific commit, if needed). Just for the sake of the completeness, v1.18.4 caused a regression on "k8s-copy-file" tests, which is tracked on CRI-O side as https://github.com/cri-o/cri-o/issues/4353. Fixes: #1080 Signed-off-by: Fabiano Fidêncio --- versions.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versions.yaml b/versions.yaml index 8a469c16d9..1ba7d2d85e 100644 --- a/versions.yaml +++ b/versions.yaml @@ -179,7 +179,7 @@ externals: description: | OCI-based Kubernetes Container Runtime Interface implementation url: "https://github.com/cri-o/cri-o" - version: "v1.18.3" + version: "v1.18.4" meta: openshift: "6273bea4c9ed788aeb3d051ebf2d030060c05b6c" crictl: 1.0.0-beta.2