Re: [neutron] ovs: multiple rows in Manager patch
Just sending response to the list in case anyone else has the same issue. On 6/17/24 1:09 PM, stream_unpicked390@simplelogin.com wrote:
Hi,
On 6/13/24 21:38, Brian Haley - haleyb.dev(a)gmail.com wrote:
Hi,
On 6/13/24 4:53 AM, stream_unpicked390@simplelogin.com wrote:
Hi Brian, On 6/12/24 23:04, Brian Haley - haleyb.dev(a)gmail.com wrote:
Hi,
On 6/12/24 12:43 PM, stream_unpicked390@simplelogin.com wrote:
Hi everyone!
this is my first time on a mailing list, so please excuse any "obvious" mistakes and feel free to correct me :)
I'm currently setting up a minimal OpenStack system manually on one server. The setup is nearly complete but I'm running into issues with neutron. After fully completing the neutron setup as mentioned in the docs, the neutron-ovs-service refuses to start, showing the error message
Sorry, but I have to ask which "docs" are you using?
thanks for your quick answer! I followed the OpenStack install guide under https://docs.openstack.org/2024.1/install/. For neutron specifically, I used the document linked under https://docs.openstack.org/neutron/2024.1/install/install-ubuntu.html.
As I mentioned, I'm currently setting up everything on just one server, the documentations scenario describes two servers. This is the only intentional diversion I made from the docs. I've been trying to setup a self-service network.
I don't see ptcp used in any of the examples here for ovsdb_connection:
I couldn't find any example of the ovsdb_connection and I don't remember modifying any value like that either. The problem existed "right out of the box". Can you point me to the part of the linked documentation where the ovsdb_connection config is discussed?
Instead of trying to go through the details of anything that might be wrong, if you are just trying to get a single-node Openstack running have you tried using devstack [0]? It would be much simpler if this is just for testing purposes. This is a production setup so devstack was out of the question. Because of our very tight constraints, we first have to set up a single node, before being able to add additional servers. Definitely not ideal.. Your hint about ovsdb_connection helped me out! While I couldn't find any setting with the name ovsdb_connection already set to an, apparently wrong, string, I set ovsdb_connection to the value mentioned by you. This probably overwrote something I couldn't find, because after restarting neutron, my issues were gone! Thanks again for looking into my issue and guiding me on the right path!
Glad it worked out, thanks for responding. -Brian
[0] https://github.com/openstack-dev/devstack.git
multiple rows in Manager patch "ptcp:6640:127.0.0.0"
Two things look wrong here, both the IP address and port. Typically this string would be "ptcp:127.0.0.1:6640" or "ptcp:0.0.0.0:6640" in ml2_conf.ini.
Thanks! I will try to take a look at the aforementioned config as soon as possible and report back!
-Brian
I dumped the ovs database which only shows one row in the Manager table. After many days of debugging and googleing I'm out of ideas how this could be solved.. I already posted this issue on serverfault (https://serverfault.com/questions/1160418/openstack-ovs-multiple-rows-in-man...), only after that post finding this mailing list!
Best regards Talooola
Hi, Sadly the problem reappeared. Apparently, just setting the config value didn't solve the issue. It is now set to "ptcp:0.0.0.0:6640". I still get the error "multiple rows in Manager match "ptcp:6640:0.0.0.0"" from neutron-openvswitch-agent. "ovs-vsctl list Manager" show the following: _uuid : b3ad8318-a54b-405e-8c9b-398b57b09fb6 connection_mode : [] external_ids : {} inactivity_probe : 10000 is_connected : false max_backoff : [] other_config : {} status : {state=BACKOFF} target : "pptcp:6640:127.0.0.1" _uuid : 2a92bee2-19e1-42b1-9688-993c08dbc790 connection_mode : [] external_ids : {} inactivity_probe : 10000 is_connected : true max_backoff : [] other_config : {} status : {bound_port="6640", n_connections="5", sec_since_connect="0", sec_since_disconnect="0"} target : "ptcp:6640:127.0.0.1" _uuid : b0643ddf-7191-4d92-9dc5-a8ef61588785 connection_mode : [] external_ids : {} inactivity_probe : 10000 is_connected : false max_backoff : [] other_config : {} status : {sec_since_connect="0", sec_since_disconnect="0"} target : "ptcp:6640:0.0.0.0" Any ideas? Like I described above, I'm trying to manually setup openstack on one server including nova, neutron, horizon, designate, keystone among others. Best regards Talooola On 6/19/24 15:15, Brian Haley - haleyb.dev(a)gmail.com wrote:
Just sending response to the list in case anyone else has the same issue.
On 6/17/24 1:09 PM, stream_unpicked390@simplelogin.com wrote:
Hi,
On 6/13/24 21:38, Brian Haley - haleyb.dev(a)gmail.com wrote:
Hi,
On 6/13/24 4:53 AM, stream_unpicked390@simplelogin.com wrote:
Hi Brian, On 6/12/24 23:04, Brian Haley - haleyb.dev(a)gmail.com wrote:
Hi,
On 6/12/24 12:43 PM, stream_unpicked390@simplelogin.com wrote:
Hi everyone!
this is my first time on a mailing list, so please excuse any "obvious" mistakes and feel free to correct me :)
I'm currently setting up a minimal OpenStack system manually on one server. The setup is nearly complete but I'm running into issues with neutron. After fully completing the neutron setup as mentioned in the docs, the neutron-ovs-service refuses to start, showing the error message
Sorry, but I have to ask which "docs" are you using?
thanks for your quick answer! I followed the OpenStack install guide under https://docs.openstack.org/2024.1/install/. For neutron specifically, I used the document linked under https://docs.openstack.org/neutron/2024.1/install/install-ubuntu.html.
As I mentioned, I'm currently setting up everything on just one server, the documentations scenario describes two servers. This is the only intentional diversion I made from the docs. I've been trying to setup a self-service network.
I don't see ptcp used in any of the examples here for ovsdb_connection:
I couldn't find any example of the ovsdb_connection and I don't remember modifying any value like that either. The problem existed "right out of the box". Can you point me to the part of the linked documentation where the ovsdb_connection config is discussed?
Instead of trying to go through the details of anything that might be wrong, if you are just trying to get a single-node Openstack running have you tried using devstack [0]? It would be much simpler if this is just for testing purposes. This is a production setup so devstack was out of the question. Because of our very tight constraints, we first have to set up a single node, before being able to add additional servers. Definitely not ideal.. Your hint about ovsdb_connection helped me out! While I couldn't find any setting with the name ovsdb_connection already set to an, apparently wrong, string, I set ovsdb_connection to the value mentioned by you. This probably overwrote something I couldn't find, because after restarting neutron, my issues were gone! Thanks again for looking into my issue and guiding me on the right path!
Glad it worked out, thanks for responding.
-Brian
[0] https://github.com/openstack-dev/devstack.git
multiple rows in Manager patch "ptcp:6640:127.0.0.0"
Two things look wrong here, both the IP address and port. Typically this string would be "ptcp:127.0.0.1:6640" or "ptcp:0.0.0.0:6640" in ml2_conf.ini.
Thanks! I will try to take a look at the aforementioned config as soon as possible and report back!
-Brian
I dumped the ovs database which only shows one row in the Manager table. After many days of debugging and googleing I'm out of ideas how this could be solved.. I already posted this issue on serverfault (https://serverfault.com/questions/1160418/openstack-ovs-multiple-rows-in-man...), only after that post finding this mailing list!
Best regards Talooola
participants (2)
-
Brian Haley
-
stream_unpicked390＠simplelogin.com