versions: Update supported cri-o version

[chavafg]

We need to update the cri-o version to the
HEAD of the release-1.10 branch, which contains a fix
to be able to test cri-o with devicemapper using a
block device.

Fixes #435.

Signed-off-by: Salvador Fuentes salvador.fuentes@intel.com

[katacontainersbot]

PSS Measurement:
Qemu: 148078 KB
Proxy: 4605 KB
Shim: 8861 KB

Memory inside container:
Total Memory: 2045972 KB
Free Memory: 2007308 KB

[katacontainersbot]

PSS Measurement:
Qemu: 146824 KB
Proxy: 4596 KB
Shim: 8869 KB

Memory inside container:
Total Memory: 2045972 KB
Free Memory: 2007432 KB

[jcvenegas]

lgtm

[amshinde]

lgtm

[amshinde]

@chavafg CI is failing

# time="2018-06-21T20:57:17Z" level=error msg="error opening storage: /dev/vdb is already part of a volume group "storage": must remove this device from any volume group or provide a different device" 

[chavafg]

@amshinde yes, I forgot to export $LVM_DEVICE on the test PR, just repushed, this time it should work

[jodh-intel]

lgtm

[katacontainersbot]

PSS Measurement:
Qemu: 142386 KB
Proxy: 4675 KB
Shim: 9089 KB

Memory inside container:
Total Memory: 2045972 KB
Free Memory: 2007308 KB

[katacontainersbot]

PSS Measurement:
Qemu: 142249 KB
Proxy: 4667 KB
Shim: 8884 KB

Memory inside container:
Total Memory: 2045972 KB
Free Memory: 2007300 KB

[codecov]

Codecov Report

Merging #436 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #436   +/-   ##
=======================================
  Coverage   63.99%   63.99%           
=======================================
  Files          87       87           
  Lines        8801     8801           
=======================================
  Hits         5632     5632           
  Misses       2564     2564           
  Partials      605      605

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9377548...09fb56c. Read the comment docs.

[jodh-intel]

Hi @chavafg - we've got a clean CI run so can we now remove the dnm label?

[chavafg]

Hi,

I've changed the cri-o version from being the latest head of the release-1.10 branch to 66788a10e57f42faf741c2f149d0ee6635063014 which is a commit from the 1.11-dev release. I re-ran the CI over the weekend and it seems that the problem is gone.
Want consensus if it is ok to move to this 1.11-dev version?
/cc @jodh-intel @sboeuf @grahamwhaley @amshinde @egernst

[sboeuf]

@chavafg which problem ? Are you talking about sporadic CRI-O failures ?
Also, moving to 1.11 means we have to move to k8s 1.11, right ? Isn't it a big change ?

[jcvenegas]

lgtm

[jcvenegas]

@chavafg I am fine if we can unlock the CI but we still need a plan to make sure latest cri-o release works.

[katacontainersbot]

PSS Measurement:
Qemu: 148751 KB
Proxy: 4713 KB
Shim: 8766 KB

Memory inside container:
Total Memory: 2045968 KB
Free Memory: 2007228 KB

[chavafg]

closing as #454 will address this.