)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"7981fd747eeb56654d3d049d1c1f3fa8a819eb27","unresolved":false,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Fix devstack with linuxbridge without l3 agent"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"The linuxbridge agent for Neutron expects that the public bridge will"},{"line_number":10,"context_line":"already be created by the time it starts. On devstack, this only occurs"},{"line_number":11,"context_line":"as part of the l3 agent configuration. If a compute node doesn\u0027t have an"},{"line_number":12,"context_line":"l3 agent and is using a linuxbridge agent, then br-ex won\u0027t be created"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"7a77a97e_0117fb54","line":9,"updated":"2016-11-21 16:41:52.000000000","message":"So maybe the issue here is the agent expects a bridge that it doesn\u0027t really need (the node does not run L3 pieces, so it\u0027s redundant)?","commit_id":"a4d4ea42adc9188ea6095dfb6faefa11ba83a77d"}],"lib/neutron_plugins/linuxbridge_agent":[{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"dda4ab79b3e1b5fb5b0362bb98aaa8bc5cdc9e67","unresolved":false,"context_lines":[{"line_number":62,"context_line":"        LB_INTERFACE_MAPPINGS\u003d$PHYSICAL_NETWORK:$LB_PHYSICAL_INTERFACE"},{"line_number":63,"context_line":"    fi"},{"line_number":64,"context_line":"    if [[ \"$PUBLIC_BRIDGE\" !\u003d \"\" ]] \u0026\u0026 [[ \"$PUBLIC_PHYSICAL_NETWORK\" !\u003d \"\" ]]; then"},{"line_number":65,"context_line":"        if is_service_enabled neutron-l3; then"},{"line_number":66,"context_line":"            iniset /$Q_PLUGIN_CONF_FILE linux_bridge bridge_mappings \"$PUBLIC_PHYSICAL_NETWORK:$PUBLIC_BRIDGE\""},{"line_number":67,"context_line":"        fi"},{"line_number":68,"context_line":"    fi"}],"source_content_type":"application/x-shellscript","patch_set":2,"id":"5a74a57a_0c1c9976","line":65,"updated":"2016-11-29 23:33:21.000000000","message":"there\u0027s no such a thing as neutron-l3 is there? I always thought we\u0027d stick with q-l3","commit_id":"7f95baa5706980a0910741693abee73abea98b89"},{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"17a0397055cb8d77a681898f673eb0c7c6956a87","unresolved":false,"context_lines":[{"line_number":62,"context_line":"        LB_INTERFACE_MAPPINGS\u003d$PHYSICAL_NETWORK:$LB_PHYSICAL_INTERFACE"},{"line_number":63,"context_line":"    fi"},{"line_number":64,"context_line":"    if [[ \"$PUBLIC_BRIDGE\" !\u003d \"\" ]] \u0026\u0026 [[ \"$PUBLIC_PHYSICAL_NETWORK\" !\u003d \"\" ]]; then"},{"line_number":65,"context_line":"        if is_service_enabled neutron-l3; then"},{"line_number":66,"context_line":"            iniset /$Q_PLUGIN_CONF_FILE linux_bridge bridge_mappings \"$PUBLIC_PHYSICAL_NETWORK:$PUBLIC_BRIDGE\""},{"line_number":67,"context_line":"        fi"},{"line_number":68,"context_line":"    fi"}],"source_content_type":"application/x-shellscript","patch_set":2,"id":"5a74a57a_18cf60b4","line":65,"in_reply_to":"5a74a57a_0c1c9976","updated":"2016-11-30 11:00:55.000000000","message":"I believe it\u0027s neutron-l3 in new devstack lib but q-l3 in the -legacy one. And this apparently breaks the latter that is still (shame on us!) used in our gates.","commit_id":"7f95baa5706980a0910741693abee73abea98b89"}]}