)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":29260,"name":"Jesper Schmitz Mouridsen","email":"jesper@schmitz.computer","username":"jsmdk"},"change_message_id":"b7bbcef1f5b7eb9790bb2518b0c447effdd3d9c4","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"4576dc58_f6d6cd7e","updated":"2022-01-07 18:27:17.000000000","message":"Is this a root cause ? https://kind.sigs.k8s.io/docs/user/known-issues/#failure-to-create-cluster-with-cgroups-v2","commit_id":"fe75ca3459a5b44b835b4157149d062526953915"},{"author":{"_account_id":34400,"name":"Michael DiPietro","email":"mdipietro@wikimedia.org"},"change_message_id":"f3c25c43f1d0c7f90ec143b1b952ad1ed9121f19","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"bffbc227_ec7e9286","updated":"2021-12-24 12:09:22.000000000","message":"This seems to get magnum running on CoreOS versions greater than 34.20210518.3.0, which I assume is where cgroups moved to v2, when I\u0027m running in devstack. I didn\u0027t have any issues when I ran it there.  Is this patch still in the works? Or is there another method of getting newer CoreOS running?\n\nThank you","commit_id":"fe75ca3459a5b44b835b4157149d062526953915"},{"author":{"_account_id":20498,"name":"Spyros Trigazis","email":"spyridon.trigazis@cern.ch","username":"strigazi"},"change_message_id":"036227a99e49b4608495c25f85b8e7aa17802922","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"317c1f15_00c05d07","updated":"2022-02-03 08:39:13.000000000","message":"Works fine with 1.20 and 1.21, for 1.22 we need other changes as well.","commit_id":"fe75ca3459a5b44b835b4157149d062526953915"},{"author":{"_account_id":20498,"name":"Spyros Trigazis","email":"spyridon.trigazis@cern.ch","username":"strigazi"},"change_message_id":"d9e03aa816666a6b015a72db3dea78f9940242bd","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"ed2864ad_bf94b190","updated":"2022-02-03 08:39:43.000000000","message":"Works fine with fcos 35\nfedora-coreos-35.20220103.3.0-openstack.x86_64","commit_id":"fe75ca3459a5b44b835b4157149d062526953915"},{"author":{"_account_id":29260,"name":"Jesper Schmitz Mouridsen","email":"jesper@schmitz.computer","username":"jsmdk"},"change_message_id":"c7663cde4f283870c04a292e021fac6ad5fc1d15","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"680f8783_0e8a7564","in_reply_to":"4576dc58_f6d6cd7e","updated":"2022-01-08 13:32:42.000000000","message":"No it is not. You can use https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/34.20210427.3.0/x86_64/fedora-coreos-34.20210427.3.0-openstack.x86_64.qcow2.xz for victoria ootb with default kubetag. Just a note\nif you have been hit by this.","commit_id":"fe75ca3459a5b44b835b4157149d062526953915"},{"author":{"_account_id":34400,"name":"Michael DiPietro","email":"mdipietro@wikimedia.org"},"change_message_id":"b8c984757369ec4c34d2d076accd6504e0aff23d","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"f5e8a600_4b2c5ae5","in_reply_to":"680f8783_0e8a7564","updated":"2022-01-10 11:32:52.000000000","message":"I don\u0027t think that is the problem that I\u0027m seeing. I\u0027m trying to run a v1.20 cluster, so the k8s part should handle cgroups v2. I can\u0027t get the cluster to finish building unless I include the patch in this review to magnum. Kubelet and kube-proxy present:\nError: statfs /sys/fs/cgroup/systemd: no such file or directory\nin their logs, and won\u0027t start. If the patch is applied they seem to start fine.\n\nI am running all this on xena if that makes a difference.","commit_id":"fe75ca3459a5b44b835b4157149d062526953915"},{"author":{"_account_id":29260,"name":"Jesper Schmitz Mouridsen","email":"jesper@schmitz.computer","username":"jsmdk"},"change_message_id":"b7bbcef1f5b7eb9790bb2518b0c447effdd3d9c4","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"a4003e81_7c91b779","in_reply_to":"bffbc227_ec7e9286","updated":"2022-01-07 18:27:17.000000000","message":"Is this a root cause ? https://kind.sigs.k8s.io/docs/user/known-issues/#failure-to-create-cluster-with-cgroups-v2","commit_id":"fe75ca3459a5b44b835b4157149d062526953915"},{"author":{"_account_id":34400,"name":"Michael DiPietro","email":"mdipietro@wikimedia.org"},"change_message_id":"3509d324ba2ffc35e0c3b1b4efef83bb624d9826","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"2a75dc35_4b15b99e","in_reply_to":"ce8eea81_1b526129","updated":"2022-01-26 11:38:08.000000000","message":"I believe I only encountered the error when I was pulling a FedoraCoreos newer than 34.20210518.3.0 regardless of the kubernetes version. I haven\u0027t tried pulling an older FedoraCoreos and running k8s \u003e\u003d 1.19. I could do that if it is useful. Though in my case it seems to be more related to the coreos version than the k8s version. If the issue is that k8s \u003c\u003d 1.18 will not work with this patch, isn\u0027t that alright? As the oldest supported k8s at this point is 1.20, and only for another month at that.\n\nThough I\u0027m probably missing something more basic. Is there a way to run a recent FedoraCoreos and a recent k8s without this patch? I assume there is and I haven\u0027t uncovered it.\n\nThank you!","commit_id":"fe75ca3459a5b44b835b4157149d062526953915"},{"author":{"_account_id":29260,"name":"Jesper Schmitz Mouridsen","email":"jesper@schmitz.computer","username":"jsmdk"},"change_message_id":"a4c7163a3671a0878c3edcb0bcb49930206d1a27","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"ce8eea81_1b526129","in_reply_to":"f5e8a600_4b2c5ae5","updated":"2022-01-10 15:49:19.000000000","message":"The https://kind.sigs.k8s.io/docs/user/known-issues/#failure-to-create-cluster-with-cgroups-v2 error is with this change and an \u003c v1.19 cluster and a cgroupv2 fcos. Perhaps their could be added a cgroup_version label/image property , so that all fcos kube_tag combinations can be supported?","commit_id":"fe75ca3459a5b44b835b4157149d062526953915"}]}