)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":36080,"name":"Erkin Mussurmankulov","display_name":"Eric","email":"mangust404@gmail.com","username":"mongoose404","status":"PS Cloud services employee"},"change_message_id":"fc28ecbd29d9fd00d03d438ec9f380f2e35ce591","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"eb5c7948_c4a88518","updated":"2026-05-28 07:28:20.000000000","message":"Hello Wu,\n\nCould you please take a look at this patch?\n\nDoes your local DevStack work without DNS in the `private` network?\n\nAlso, I\u0027ve inspected the Zuul jobs. Somehow, it gets two default routes from cloud-init:\n\n```\n| Route |   Destination   |    Gateway    |     Genmask     | Interface | Flags |\n+-------+-----------------+---------------+-----------------+-----------+-------+\n|   0   |     0.0.0.0     |    10.1.0.1   |     0.0.0.0     |    ens3   |   UG  |\n|   1   |     0.0.0.0     | 192.168.254.1 |     0.0.0.0     |    ens4   |   UG  |\n|   2   |     8.8.8.8     | 192.168.254.1 | 255.255.255.255 |    ens4   |  UGH  |\n|   3   |     10.1.0.0    |    0.0.0.0    | 255.255.255.192 |    ens3   |   U   |\n|   4   |     10.1.0.1    |    0.0.0.0    | 255.255.255.255 |    ens3   |   UH  |\n|   5   |     10.1.0.2    |    0.0.0.0    | 255.255.255.255 |    ens3   |   UH  |\n|   6   |    127.0.0.1    |    0.0.0.0    | 255.255.255.255 |    ens3   |   UH  |\n|   7   | 169.254.169.254 |    10.1.0.2   | 255.255.255.255 |    ens3   |  UGH  |\n|   8   | 169.254.169.254 | 192.168.254.2 | 255.255.255.255 |    ens4   |  UGH  |\n|   9   |  192.168.254.0  |    0.0.0.0    |  255.255.255.0  |    ens4   |   U   |\n|   10  |  192.168.254.1  |    0.0.0.0    | 255.255.255.255 |    ens4   |   UH  |\n|   11  |  192.168.254.2  |    0.0.0.0    | 255.255.255.255 |    ens4   |   UH  |\n+-------+-----------------+---------------+-----------------+-----------+-------+\n```\n\nHaving two default routes is not correct behavior. Using the `trove-mgmt` network for internet access isn\u0027t correct either. But somehow, it works 🤔\n\nWe\u0027ll probably need to revisit this issue later. Right now, we at least need to make local DevStack setups work properly.","commit_id":"9715c3e10e238ad1ea6dad4d995f1bcc92f7ce9a"},{"author":{"_account_id":26285,"name":"wu.chunyang","email":"wchy1001@gmail.com","username":"wu.chunyang"},"change_message_id":"ddf44fab93bd12c0d2ad926b28735a30afa58c6d","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"c11eaa12_dceaa5c8","in_reply_to":"26fb1617_e61d96c0","updated":"2026-06-09 02:29:52.000000000","message":"When designing the Trove network, trove-mgmt handles all network access, including trove-guestagent deployment, Docker Hub access and OpenStack control plane traffic. Since we cannot predict how users configure their private networks, the user network should not undertake this role.","commit_id":"9715c3e10e238ad1ea6dad4d995f1bcc92f7ce9a"},{"author":{"_account_id":26285,"name":"wu.chunyang","email":"wchy1001@gmail.com","username":"wu.chunyang"},"change_message_id":"a2f955af3aaaf375c4327bfeb989072fd8a75301","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"26fb1617_e61d96c0","in_reply_to":"eb5c7948_c4a88518","updated":"2026-06-09 02:23:17.000000000","message":"hello, The default DNS should work correctly, because the private network is associated with the router, and the router has the external network access.\n\nFrom the cloud init logs: the ens3 is the management network adapter, and the ens4 is the user network adapter, after the trove-agent starts, the ens4 will be set down before performing all network operations, as a result, the default routes via the ens4 will be deleted by the kernel.\n\nSo, what problem have you encountered?\n\nmore information: https://github.com/openstack/trove/blob/master/trove/cmd/guest.py#L77","commit_id":"9715c3e10e238ad1ea6dad4d995f1bcc92f7ce9a"}],"devstack/settings":[{"author":{"_account_id":37598,"name":"Ivan Anfimov","display_name":"Ivan Anfimov","email":"lazekteam@gmail.com","username":"anfimovir"},"change_message_id":"9dfe5f3718a2d3fe87e75c4d8706e84f2fa804bc","unresolved":true,"context_lines":[{"line_number":104,"context_line":"AMQP_PORT\u003d${AMQP_PORT:-5672}"},{"line_number":105,"context_line":"REGISTRY_PORT\u003d${REGISTRY_PORT:-4000}"},{"line_number":106,"context_line":""},{"line_number":107,"context_line":"TROVE_DNS\u003d${TROVE_DNS:-8.8.8.8}"}],"source_content_type":"application/octet-stream","patch_set":1,"id":"c6424308_81da1619","line":107,"updated":"2026-05-28 09:28:24.000000000","message":"May be add alternative DNS too? 1.1.1.1","commit_id":"9715c3e10e238ad1ea6dad4d995f1bcc92f7ce9a"},{"author":{"_account_id":36080,"name":"Erkin Mussurmankulov","display_name":"Eric","email":"mangust404@gmail.com","username":"mongoose404","status":"PS Cloud services employee"},"change_message_id":"78c8fc74270acd59bdfaa7cec936dd60518d758b","unresolved":false,"context_lines":[{"line_number":104,"context_line":"AMQP_PORT\u003d${AMQP_PORT:-5672}"},{"line_number":105,"context_line":"REGISTRY_PORT\u003d${REGISTRY_PORT:-4000}"},{"line_number":106,"context_line":""},{"line_number":107,"context_line":"TROVE_DNS\u003d${TROVE_DNS:-8.8.8.8}"}],"source_content_type":"application/octet-stream","patch_set":1,"id":"e835bad3_be6f21b9","line":107,"in_reply_to":"c6424308_81da1619","updated":"2026-05-28 09:36:02.000000000","message":"For a long time, trove-mgmt has worked on a single `8.8.8.8`. I think it\u0027s fine for a testing environment. It either works or doesn\u0027t.\nIf it doesn\u0027t work, we\u0027ll see it easily and just wait until it goes up. If we\u0027ll add a second DNS, some timeouts during execution may occur, which may produce some ambiguity in test results.","commit_id":"9715c3e10e238ad1ea6dad4d995f1bcc92f7ce9a"}]}