Peter Hunt
Peter Hunt
@saschagrunert did you still want to work on this?
> Can't the default image of crio be read in kubeadm-init.yaml like previous versions? I'm under the impression this didn't didn't work as you're describing. my understanding is that kubeadm...
hm, we're getting this error: ``` TASK [enable and start CRI-O] ************************************************** task path: /go/src/github.com/cri-o/cri-o/contrib/test/integration/e2e-base.yml:25 fatal: [localhost]: FAILED! => {"changed": false, "msg": "Error loading unit file 'crio': org.freedesktop.DBus.Error.InvalidArgs \"Invalid argument\""}...
I think some of those failures were infra failures. I'm going to re-run to see what the state of the world actually is /retest
/test e2e_fedora
I am sorry I have not had a chance to look at this. I will try later today
hey @r10r sorry again, this keeps falling off of my radar. what happens when you apply this patch: ``` diff --git a/contrib/test/integration/build/cri-o.yml b/contrib/test/integration/build/cri-o.yml index 2aa23e465..b447d41cd 100644 --- a/contrib/test/integration/build/cri-o.yml +++ b/contrib/test/integration/build/cri-o.yml...
do we still want this @mrunalp @saschagrunert
/retest-required