)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"fbb24e0ccea3376f4272307b5753a1e54717ba57","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"6e7b3765_80fbfc7e","updated":"2025-06-11 12:31:43.000000000","message":"Failure is completely unrelated to this patch.  This patch LGTM.","commit_id":"bc314a5352698077c5a730c73bfda162fd9794ba"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"43ceb5b202765452132158da1bead7950aa73144","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"da3e53ab_461f431f","updated":"2025-06-12 12:53:00.000000000","message":"Looks like this patch in octavia master fixes the octavia jobs:\nhttps://review.opendev.org/c/openstack/octavia/+/952287\n\nIt\u0027s been approved and is in recheck now.","commit_id":"bc314a5352698077c5a730c73bfda162fd9794ba"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"ee90f6666d562aa1b6097b0fe1300a759640f69f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"5191bf39_a996b50d","updated":"2025-06-12 14:52:01.000000000","message":"Word on the street is that Canonical released a fix for Jammy that should allow the octavia job to run.","commit_id":"bc314a5352698077c5a730c73bfda162fd9794ba"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"59d9f91a5ae15c4da9f68f423842143c20e5e674","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"8fac7707_194320f3","updated":"2025-06-12 15:47:30.000000000","message":"octavia is looking good, but the functional tests are failing on this patch.  A bunch of requests.exceptions.ReadTimeout: HTTPConnectionPool(host\u003d\u0027213.32.72.107\u0027, port\u003d80): Read timed out. (read timeout\u003d10) ... not sure what\u0027s up with that.","commit_id":"bc314a5352698077c5a730c73bfda162fd9794ba"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"b9b5caacd179d1a644469eccc3ddc3396a22fe34","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"158ef456_53ad6151","updated":"2025-06-11 12:31:14.000000000","message":"recheck octavia-v2-dsvm-tls-barbican - failure in setUpClass (octavia_tempest_plugin.tests.barbican_scenario.v2.test_tls_barbican.TLSWithBarbicanTest) - show_loadbalancer provisioning_status failed to update to ACTIVE within the required time 900. Current status of show_loadbalancer: PENDING_CREATE","commit_id":"bc314a5352698077c5a730c73bfda162fd9794ba"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"2d255b23cc391b81733998a0890ea230b043cdf9","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"f8eed7f3_3dd0deaa","updated":"2025-06-12 14:52:48.000000000","message":"recheck octavia-v2-dsvm-tls-barbican - upstream fix has been released for jammy","commit_id":"bc314a5352698077c5a730c73bfda162fd9794ba"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"c72159c94943d1bf347ed5de523da6178d9c23a9","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"454418fb_fb817f7e","updated":"2025-06-09 20:07:25.000000000","message":"recheck requests.exceptions.ReadTimeout: HTTPConnectionPool(host\u003d\u0027213.32.77.196\u0027, port\u003d80): Read timed out. (read timeout\u003d10)","commit_id":"bc314a5352698077c5a730c73bfda162fd9794ba"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"e36c1bc76a1ccf61625ee684903e170027952a93","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"8cc81856_01698369","in_reply_to":"13770eca_88e13369","updated":"2025-06-12 17:19:41.000000000","message":"I found the timeout in a config barbican-functional.conf [1][2]:\n\n```\n# use this to increase the timeout (in seconds) when debugging API calls\n#timeout\u003d10\n```\n\nand I\u0027m trying out a change under this one to increase the timeout to 60 seconds based on the default HTTP timeout in Tempest:\n\nhttps://review.opendev.org/c/openstack/barbican/+/952491\n\n[1] https://zuul.opendev.org/t/openstack/build/c2fafde049a9426394d9c4c1fca65efc/log/controller/logs/etc/barbican/barbican-functional_conf.txt#59-60\n[2] https://github.com/openstack/barbican/blob/d98891faee8c6adf85f85ae006ccb903999cb7c8/functionaltests/common/config.py#L77","commit_id":"bc314a5352698077c5a730c73bfda162fd9794ba"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"9456761e5ee90abe8439c47f950f996b22cfee44","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"cebf09bd_7305f740","in_reply_to":"8cc81856_01698369","updated":"2025-06-12 18:44:53.000000000","message":"Looks like the change worked, I see the `timeout\u003d60` in the `barbican-functional.conf`:\n\nhttps://zuul.opendev.org/t/openstack/build/68e38ed91476432ba5ff1fd67cd98dbd/log/controller/logs/etc/barbican/barbican-functional_conf.txt#59-60","commit_id":"bc314a5352698077c5a730c73bfda162fd9794ba"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"805970403abe59361a0e3bae1610767c96f60a3b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"13770eca_88e13369","in_reply_to":"8fac7707_194320f3","updated":"2025-06-12 16:57:46.000000000","message":"In my experience, this is a fairly common intermittent failure in CI in general. Presumably caused by load/resource contention on the CI node. I note a lot of CI jobs use the word \"functional\" to mean a real deployment with HTTP requests to the services. Whereas in other projects, like Nova, the word \"functional\" means a self-contained mocked environment where API request interactions are simulated.\n\nSo here we see for example a HTTP request to delete a secret does not receive a response from Barbican within N seconds. I do notice that the timeout is set to only 10 seconds, which is much lower than what I\u0027m used to seeing. Usually I see this set to 60 seconds or 90 seconds. So that is something I can look into where/why that\u0027s set to 10.","commit_id":"bc314a5352698077c5a730c73bfda162fd9794ba"}]}