)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"ccbb9f5e0bacf33cbfa345a407c11fd7f6d4cea2","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"f1e43edc_3e285758","updated":"2023-06-29 13:52:48.000000000","message":"recheck\n\n\u003e sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server on socket \"/tmp/tmpirzhd6ub/.s.PGSQL.9824\" failed: FATAL:  sorry, too many clients already","commit_id":"7185bad1dff7b170610cb059628e31ca8429d1b5"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"ff4b735e5dee7a98332ac8928f799c74b95a5a4d","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"9f400e68_c9f028aa","updated":"2023-09-13 07:49:24.000000000","message":"Actually maybe this should be abandoned as the release has been superceded by 14.0.0, but that seems to have even more failures https://review.opendev.org/c/openstack/requirements/+/893043\n\nSo maybe oslo.db should get more testing before it gets released?","commit_id":"2f62f347b8a01fa0700ad44f830daa0d75f81c55"},{"author":{"_account_id":28522,"name":"Hervé Beraud","email":"herveberaud.pro@gmail.com","username":"hberaud"},"change_message_id":"527adb76b3c1d8399c6972e417b40911f0406377","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"6b1f2573_60f48f1c","updated":"2023-09-12 09:42:35.000000000","message":"Hello,\n\nHere are some summarize of the errors met in the cross tests job.\n\n- The aodh error seems related to a connection error with a postgres database where too many connections seems to occur, and oslo.db doesn\u0027t seems to be present in the stack. (psycopg2.OperationalError: connection to server on socket \"/tmp/tmpus9gy3wq/.s.PGSQL.9824\" failed: FATAL:  sorry, too many clients already), but sqlalchemy is present.\n- the heat error seems to be an internal heat error related to a session that is already begun, oslo.db seems not present in the stack (eat.common.exception.ResourceFailure: InvalidRequestError: resources.HostKeys: A transaction is already begun on this Session.), but sqlalchemy is present.\n- The masakari error seems legit, and is related to oslo.db. Indeed the migration module of oslo.db has been removed and masakari still try to import it, so masakari needs refactor to fix that error https://opendev.org/openstack/oslo.db/commit/94d6e24ca19b0116eed00d5ccdb8a538918c6dcf\n- the manila error seems also legit, and is related to a class import not present in oslo.db, I think this issue is related to the alembic version pulled by oslo.db where this class has been surely removed. (AttributeError: module \u0027oslo_db.sqlalchemy.test_migrations\u0027 has no attribute \u0027WalkVersionsMixin\u0027), in this case manile would need some refactors.","commit_id":"2f62f347b8a01fa0700ad44f830daa0d75f81c55"},{"author":{"_account_id":8313,"name":"Lajos Katona","display_name":"lajoskatona","email":"katonalala@gmail.com","username":"elajkat","status":"Ericsson Software Technology"},"change_message_id":"63f5d438dfa350cad95fb9049b845907f121223b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"99dc6ad8_7bba074b","updated":"2023-09-12 11:17:37.000000000","message":"This can be dropped as https://review.opendev.org/c/openstack/requirements/+/879743 proposes the same oslo.db bump together with SQLAlchemy bump, am I right?","commit_id":"2f62f347b8a01fa0700ad44f830daa0d75f81c55"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"8498fcc23c42c70ffd199d9184e39ed02feb2014","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"53a83cb2_ef7389c9","in_reply_to":"31ad1c79_65844181","updated":"2023-09-14 08:45:16.000000000","message":"Yes, exactly. We should have got all projects up-to-speed in bobcat but it was nigh on impossible to get some projects to merge my patches 😞","commit_id":"2f62f347b8a01fa0700ad44f830daa0d75f81c55"},{"author":{"_account_id":8313,"name":"Lajos Katona","display_name":"lajoskatona","email":"katonalala@gmail.com","username":"elajkat","status":"Ericsson Software Technology"},"change_message_id":"0a9c3eee666375018c74849dd0e2208709d67696","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"08fdc7a4_e8817db8","in_reply_to":"53a83cb2_ef7389c9","updated":"2023-09-14 11:13:21.000000000","message":"it can be a topic for the PTG to share this responsibilty as it is not just your one man task.","commit_id":"2f62f347b8a01fa0700ad44f830daa0d75f81c55"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"76e9dc04b6034d6253bae7e30d80ea20e7e71613","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"7273e319_dfe55670","in_reply_to":"99dc6ad8_7bba074b","updated":"2023-09-13 07:40:46.000000000","message":"I\u0027m not sure, I don\u0027t think the world is ready for SQLA 2.0 yet, so if we can get this in first, it would still be some progress.","commit_id":"2f62f347b8a01fa0700ad44f830daa0d75f81c55"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"7905e0d445c87d7f15ca2e97b918c7d07e9bde3f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"d26f95b0_57bb83eb","in_reply_to":"9f400e68_c9f028aa","updated":"2023-09-13 14:16:53.000000000","message":"\u003e Actually maybe this should be abandoned as the release has been superceded by 14.0.0, but that seems to have even more failures https://review.opendev.org/c/openstack/requirements/+/893043\n\nI think this can be abandoned, yes. There are almost no non-bugfix changes in 14.0.0: the only significant change (and the reason for the major version bump) was the removal of MySQL NDB support which was never implemented in other projects. I would wager that any additional failures are likely as a result of regressions in the projects and if this was now rechecked we\u0027d see the same failure mode.\n\n\u003e So maybe oslo.db should get more testing before it gets released?\n\nI think they will need to be done together, tbh. oslo.db 13.x and later doesn\u0027t work with sqlalchemy \u003c 2, and earlier version don\u0027t work with \u003e\u003d 2 (we weren\u0027t able to make a version that supported both). It\u0027s going to have to be a big bang upgrade, unfortunately.","commit_id":"2f62f347b8a01fa0700ad44f830daa0d75f81c55"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"831eca572b9269c91029aab72ad5532f93fded1a","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"31ad1c79_65844181","in_reply_to":"d26f95b0_57bb83eb","updated":"2023-09-13 18:38:54.000000000","message":"\u003e \u003e So maybe oslo.db should get more testing before it gets released?\n\u003e \n\u003e I think they will need to be done together, tbh. oslo.db 13.x and later doesn\u0027t work with sqlalchemy \u003c 2, and earlier version don\u0027t work with \u003e\u003d 2 (we weren\u0027t able to make a version that supported both). It\u0027s going to have to be a big bang upgrade, unfortunately.\n\noh, that\u0027s the first time I hear this. so oslo.db\u003e\u003d13 shouldn\u0027t be part of bobcat or any other release until all projects catch up. or someone decides to drop lagging projects from the release instead","commit_id":"2f62f347b8a01fa0700ad44f830daa0d75f81c55"}]}