)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":2463,"name":"Florian Haas","email":"florian.haas@cleura.com","username":"fghaas"},"change_message_id":"9610c850b4bdc40f8ac8668317719d41cb31e03e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"d39510e5_7874c8ef","updated":"2021-11-23 19:43:24.000000000","message":"Just got bitten by this bug myself, and since the Zuul logs from back in June are no longer available so there\u0027s no way to tell what exactly went wrong in the gate, I gave a recheck a try.\n\nThis now breaks because the _OID_NAMES attribute has been removed from cryptography.x509.oid in https://github.com/pyca/cryptography/pull/6272, which landed in Cryptogaphy 35.0.0, and https://opendev.org/openstack/requirements/raw/branch/master/upper-constraints.txt now references 36.0.0.\n\nSo, I guess magnum/magnum/common/x509/validator.py needs a rewrite before this can land?","commit_id":"52d573657af9b59454be7fe42f06fd36c6205bec"},{"author":{"_account_id":2463,"name":"Florian Haas","email":"florian.haas@cleura.com","username":"fghaas"},"change_message_id":"f0054e7fc33554b9d644ae7768bcc3ef0a2514a8","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"0ff92531_513ff00b","updated":"2021-11-23 18:49:03.000000000","message":"recheck","commit_id":"52d573657af9b59454be7fe42f06fd36c6205bec"},{"author":{"_account_id":2463,"name":"Florian Haas","email":"florian.haas@cleura.com","username":"fghaas"},"change_message_id":"cdfb28f009ff059a9b5df825a1b76f098eead54b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"56b0ccd3_8eb84666","updated":"2021-11-23 19:56:42.000000000","message":"Found change I44407703fbcf2da97c29a28043520c781ef4c3b2 which should address the change in cryptography, and took the liberty to rebase this change on that.","commit_id":"27b798222f1a96519c6c5b8d95ac9d2b30088f6f"},{"author":{"_account_id":2463,"name":"Florian Haas","email":"florian.haas@cleura.com","username":"fghaas"},"change_message_id":"262c897049a64812ea377743a500d77a7dc1b007","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"8d106c16_0efc2597","updated":"2021-11-24 12:51:37.000000000","message":"To whom it may concern: I have now cherry-picked this change\n\n* to stable/xena (https://review.opendev.org/c/openstack/magnum/+/819090) and stable/victora (https://review.opendev.org/c/openstack/magnum/+/819062), where it applies cleanly and passes all tests\n* to stable/wallaby (https://review.opendev.org/c/openstack/magnum/+/819092), where it also passes all tests if applied on top of https://review.opendev.org/c/openstack/magnum/+/783249.\n\nSo, given the fact that this change has already received a +2 and a +W and subsequently fell victim to gate breakage (I think), and it\u0027s a regression for something that was already fixed once in Ib93a7c0f761d047da3408703a5cf4208821acb33, could this please be given a fresh review?\n\nRight now it looks like the deal breaker in master is really the change to the cryptography dependency. One part of this is addressed by https://review.opendev.org/c/openstack/magnum/+/817908 (for cryptography 35.0.0) addresses. \n\nHowever, as of cryptography 36.0.0 (released on 2021-11-21) we\u0027re seeing an additional error:\n\n    TypeError: Key must be an rsa, dsa, ec, ed25519, or ed448 private key.\n\nAn additional change to address that appears to be necessary, though I\u0027ve looked into the code and I can\u0027t quite make sense of what that change should be. :(\n\n","commit_id":"27b798222f1a96519c6c5b8d95ac9d2b30088f6f"},{"author":{"_account_id":2463,"name":"Florian Haas","email":"florian.haas@cleura.com","username":"fghaas"},"change_message_id":"35010818df43db5b2c8df5db4fc8509206afdf27","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"e364f430_fe69b42a","in_reply_to":"8d106c16_0efc2597","updated":"2021-11-24 12:53:13.000000000","message":"Ugh, scratch the superfluous \"addresses\" in the prior comment please (botched edit).","commit_id":"27b798222f1a96519c6c5b8d95ac9d2b30088f6f"},{"author":{"_account_id":2463,"name":"Florian Haas","email":"florian.haas@cleura.com","username":"fghaas"},"change_message_id":"84ab430c4e10de44edbc3f878e5d114fac43ba01","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"42d1520d_143b01a3","updated":"2021-11-26 07:39:04.000000000","message":"Since this is labelled Backport-Candidate: this change is a clean cherry-pick to all stable branches back to Train; I\u0027ve submitted backport changes to all of them.\n\nThe change that broke this (Ibbed59bc135969174a20e5243ff8464908801a23) landed in the Train cycle, so Stein and earlier releases do not need a backport.","commit_id":"679a174a0a630b5670dc38699370e61a6c056446"}],"magnum/drivers/common/templates/kubernetes/fragments/write-heat-params.sh":[{"author":{"_account_id":20498,"name":"Spyros Trigazis","email":"spyridon.trigazis@cern.ch","username":"strigazi"},"change_message_id":"8a2c7c938859c65da89b9c16371b63536de42668","unresolved":true,"context_lines":[{"line_number":61,"context_line":"PODS_NETWORK_CIDR\u003d\"$PODS_NETWORK_CIDR\""},{"line_number":62,"context_line":"KUBE_VERSION\u003d\"$KUBE_VERSION\""},{"line_number":63,"context_line":"TRUSTEE_USER_ID\u003d\"$TRUSTEE_USER_ID\""},{"line_number":64,"context_line":"TRUSTEE_USERNAME\u003d\"$TRUSTEE_USERNAME\u003d\""},{"line_number":65,"context_line":"TRUSTEE_PASSWORD\u003d\"$TRUSTEE_PASSWORD\""},{"line_number":66,"context_line":"TRUSTEE_DOMAIN_ID\u003d\"$TRUSTEE_DOMAIN_ID\""},{"line_number":67,"context_line":"TRUST_ID\u003d\"$TRUST_ID\""}],"source_content_type":"text/x-sh","patch_set":1,"id":"0a3d0550_cefb8a35","line":64,"range":{"start_line":64,"start_character":35,"end_line":64,"end_character":36},"updated":"2021-01-13 11:58:46.000000000","message":"typo","commit_id":"3d5f624da22dbf287ad38a2687bc4830b0dcae3a"}]}