)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":25701,"name":"Yasufumi Ogawa","email":"yasufum.o@gmail.com","username":"yasufum"},"change_message_id":"e0b685126fb866d3ea8132d665847e55198af0d0","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"2362ee05_cd4fa498","updated":"2026-08-10 06:12:57.000000000","message":"recheck - for an infra failure.","commit_id":"2b6e9040ff0190984cfc178667281ddd5e786ccb"},{"author":{"_account_id":25701,"name":"Yasufumi Ogawa","email":"yasufum.o@gmail.com","username":"yasufum"},"change_message_id":"3047914070f85181945a788bfb38401b90197c4b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"86957488_12f1e84c","updated":"2026-08-12 12:29:43.000000000","message":"recheck - for an infra failure.","commit_id":"2b6e9040ff0190984cfc178667281ddd5e786ccb"}],"devstack/local.conf.kubernetes":[{"author":{"_account_id":36672,"name":"Shivam Shukla","display_name":"Shivam Shukla","email":"shivam.shukla3@india.nec.com","username":"shivam.shukla3"},"change_message_id":"a7fd4c209621cf9e389f8601ba19d5376aa3f480","unresolved":true,"context_lines":[{"line_number":70,"context_line":"K8S_VERSION\u003d\"1.34.2\""},{"line_number":71,"context_line":"K8S_TOKEN\u003d\"9agf12.zsu5uh2m4pzt3qba\""},{"line_number":72,"context_line":"CONTAINER_ENGINE\u003d\"crio\""},{"line_number":73,"context_line":"CRIO_VERSION\u003d\"1.32.1\""},{"line_number":74,"context_line":""},{"line_number":75,"context_line":"# The plugin points kubeadm at the etcd deployed by devstack, and kubeadm 1.34"},{"line_number":76,"context_line":"# refuses an external etcd older than 3.5.24-0. devstack still defaults to"}],"source_content_type":"application/octet-stream","patch_set":3,"id":"37a454a2_ce59ce22","line":73,"updated":"2026-08-16 12:03:53.000000000","message":"Thank you for the fix. Please see my comment below.\n\nAs per CRI-O’s compatibility matrix (https://github.com/cri-o/cri-o#compatibility-matrix-cri-o--kubernetes), CRI-O follows the Kubernetes release cycles with respect to its minor versions which means CRI-O and Kubernetes minor versions are meant to match. Here, K8S_VERSION is bumped to 1.34 but CRIO_VERSION only to 1.32. \n\nIs there any reason for keeping CRIO_VERSION at 1.32.1 instead of matching the Kubernetes version?","commit_id":"2b6e9040ff0190984cfc178667281ddd5e786ccb"},{"author":{"_account_id":25701,"name":"Yasufumi Ogawa","email":"yasufum.o@gmail.com","username":"yasufum"},"change_message_id":"df60f2f3f40e1c99934c210c4bc81aef4e253b16","unresolved":true,"context_lines":[{"line_number":70,"context_line":"K8S_VERSION\u003d\"1.34.2\""},{"line_number":71,"context_line":"K8S_TOKEN\u003d\"9agf12.zsu5uh2m4pzt3qba\""},{"line_number":72,"context_line":"CONTAINER_ENGINE\u003d\"crio\""},{"line_number":73,"context_line":"CRIO_VERSION\u003d\"1.32.1\""},{"line_number":74,"context_line":""},{"line_number":75,"context_line":"# The plugin points kubeadm at the etcd deployed by devstack, and kubeadm 1.34"},{"line_number":76,"context_line":"# refuses an external etcd older than 3.5.24-0. devstack still defaults to"}],"source_content_type":"application/octet-stream","patch_set":3,"id":"006c368b_fd9d19d2","line":73,"in_reply_to":"37a454a2_ce59ce22","updated":"2026-08-25 23:07:06.000000000","message":"@shivam.shukla3@india.nec.com, thank you for the review.\n\nYou are right, there is no good reason to keep CRIO_VERSION at 1.32.1.\nIt was simply carried over from the default of devstack-plugin-container\n(CRIO_VERSION\u003d${CRIO_VERSION:-\"1.32.1\"} in its settings), and I did not\nrevisit it when bumping K8S_VERSION to 1.34.2. As you pointed out.","commit_id":"2b6e9040ff0190984cfc178667281ddd5e786ccb"}]}