)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":36174,"name":"yosef","display_name":"yosal","email":"flaslnm@gmail.com","username":"theYosal"},"change_message_id":"de8e73be3cf36376f84f2f3631b05a59b0a39dc1","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"e8ceaa6f_b44ed56a","updated":"2024-11-19 14:20:29.000000000","message":"I have seen a problem with this, will fix it later","commit_id":"e23c8592761a3cf43be3886fc466a64efb611df1"},{"author":{"_account_id":22629,"name":"Michal Nasiadka","email":"mnasiadka@gmail.com","username":"mnasiadka"},"change_message_id":"619b48745a4f5515c08dce1f654257b5943fb597","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"2d50a2dc_e08c73d4","updated":"2024-11-18 05:12:40.000000000","message":"Won’t this create another remote and still leave the old one if that gets executed on existing cluster?","commit_id":"e23c8592761a3cf43be3886fc466a64efb611df1"},{"author":{"_account_id":36174,"name":"yosef","display_name":"yosal","email":"flaslnm@gmail.com","username":"theYosal"},"change_message_id":"86c4e32334befd71653a5c4bd9caf96bd3eb415b","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"4ea64002_7dd48d5f","in_reply_to":"191951d3_e7de3f9d","updated":"2024-11-19 10:24:48.000000000","message":"Now I see what you mean. Would changing the ovn_nb_command and ovn_sb_command remotes to 0.0.0.0 be a simpler solution, or should we approach it with idempotency in mind?","commit_id":"e23c8592761a3cf43be3886fc466a64efb611df1"},{"author":{"_account_id":36174,"name":"yosef","display_name":"yosal","email":"flaslnm@gmail.com","username":"theYosal"},"change_message_id":"06e4da56d3ec6050e6beba34d637786d285f3dbc","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"aa9cbf5e_e913fb14","in_reply_to":"2d50a2dc_e08c73d4","updated":"2024-11-18 08:18:38.000000000","message":"Hi Michal,\nCurrently using this approach on production, changed from 0.0.0.0 to api_address, no issues so far.","commit_id":"e23c8592761a3cf43be3886fc466a64efb611df1"},{"author":{"_account_id":36174,"name":"yosef","display_name":"yosal","email":"flaslnm@gmail.com","username":"theYosal"},"change_message_id":"51a897348ded3a11e7ea124e40d8b3a4b107a1ed","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"7e8b67d5_b47a0bfb","in_reply_to":"4ea64002_7dd48d5f","updated":"2024-11-19 11:38:00.000000000","message":"Oh I rechecked and it will only set on record 0, meaning it will not add a new record in connections table, only editing the existing one!!!","commit_id":"e23c8592761a3cf43be3886fc466a64efb611df1"},{"author":{"_account_id":36174,"name":"yosef","display_name":"yosal","email":"flaslnm@gmail.com","username":"theYosal"},"change_message_id":"af4cef0ddcac57f25ae2386269b045697a568b4b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"6e4eb3c8_c372a6ea","in_reply_to":"6092b34e_abb4142b","updated":"2024-11-20 07:55:00.000000000","message":"Changed the patch, Now it has deleted --remote from ovsdb command which ovn-ctl creates, meaning there would be only one remote set on connections table on 0.0.0.0 with probe interval and other options, only downside is that if you delete connections table accidentally it would have no exposed port.","commit_id":"e23c8592761a3cf43be3886fc466a64efb611df1"},{"author":{"_account_id":36174,"name":"yosef","display_name":"yosal","email":"flaslnm@gmail.com","username":"theYosal"},"change_message_id":"38f85fb8e082e860db37977bdec4460c23b2b4c1","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"6092b34e_abb4142b","in_reply_to":"7e8b67d5_b47a0bfb","updated":"2024-11-20 06:42:54.000000000","message":"Ok There is a problem here, in clustered mode setting it on api_address will cause cluster to go down! this table is shared and only 1 record, so when you are using a specific address it will not work on other 2 nodes, \nI guess the only option is to change --remote on ovn-ctl to host on 0.0.0.0?","commit_id":"e23c8592761a3cf43be3886fc466a64efb611df1"},{"author":{"_account_id":22629,"name":"Michal Nasiadka","email":"mnasiadka@gmail.com","username":"mnasiadka"},"change_message_id":"10e2ff148121235c01c94c33c069972f9fcc15b1","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"191951d3_e7de3f9d","in_reply_to":"aa9cbf5e_e913fb14","updated":"2024-11-18 08:31:46.000000000","message":"This is not the answer to my question - have you ran that on existing cluster?","commit_id":"e23c8592761a3cf43be3886fc466a64efb611df1"},{"author":{"_account_id":36174,"name":"yosef","display_name":"yosal","email":"flaslnm@gmail.com","username":"theYosal"},"change_message_id":"4a5f2558cdf3a0b0532cb6c4eaa4bf27025dc2e9","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"cddf86c6_5664c083","updated":"2024-11-25 15:23:17.000000000","message":"RECHECK pull rate limit on docker","commit_id":"3324b3b8d679c6993586536c2ce422281c113cb8"},{"author":{"_account_id":14200,"name":"Maksim Malchuk","email":"maksim.malchuk@gmail.com","username":"mmalchuk"},"change_message_id":"339d6d44d365d01b8048c2e2d36605408ab8f1d8","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"7d4a679b_610c9275","updated":"2025-01-13 12:45:00.000000000","message":"should we notice an existing users than the server now listen on all IPs? the reno is missing.","commit_id":"3324b3b8d679c6993586536c2ce422281c113cb8"},{"author":{"_account_id":14200,"name":"Maksim Malchuk","email":"maksim.malchuk@gmail.com","username":"mmalchuk"},"change_message_id":"14807b8ec96791202341ee4ed18bbd1bd360f420","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"cb8a0f25_3f3d9f8c","in_reply_to":"3e34eabf_c02db42f","updated":"2025-01-21 11:43:39.000000000","message":"sure, it listen only on \u0027api_interface_address\u0027 ip","commit_id":"3324b3b8d679c6993586536c2ce422281c113cb8"},{"author":{"_account_id":14200,"name":"Maksim Malchuk","email":"maksim.malchuk@gmail.com","username":"mmalchuk"},"change_message_id":"f597899aa5c8918274b6e6a8a375278799ef3cb1","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"4ff85602_d20f1293","in_reply_to":"70eff6f8_7b59d3ab","updated":"2025-01-24 07:07:32.000000000","message":"ack","commit_id":"3324b3b8d679c6993586536c2ce422281c113cb8"},{"author":{"_account_id":36174,"name":"yosef","display_name":"yosal","email":"flaslnm@gmail.com","username":"theYosal"},"change_message_id":"20051f5ade63ca1e18e304c335d8989c836a2057","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"3e34eabf_c02db42f","in_reply_to":"7d4a679b_610c9275","updated":"2025-01-17 16:33:07.000000000","message":"Hi Maksim, \nYou are implying that the current deployment does not listens on all IPS? Im sure it is exposed on all IPs already!","commit_id":"3324b3b8d679c6993586536c2ce422281c113cb8"},{"author":{"_account_id":36174,"name":"yosef","display_name":"yosal","email":"flaslnm@gmail.com","username":"theYosal"},"change_message_id":"41350c81d4fb1f8c52930a64c681b8d00f21b4d8","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"70eff6f8_7b59d3ab","in_reply_to":"cb8a0f25_3f3d9f8c","updated":"2025-01-22 13:11:16.000000000","message":"Thank you for clarification,\nAlthough every single time we are configuring 0.0.0.0 as remotes in ovn-db role?\n\nhttps://github.com/openstack/kolla-ansible/blob/master/ansible/roles/ovn-db/tasks/bootstrap-db.yml#L22\nhttps://github.com/openstack/kolla-ansible/blob/d99b080c980b191387ac5b7751b0c7f519f5068c/ansible/roles/ovn-db/tasks/bootstrap-db.yml#L31\n\n\nThis shows that we are configuring ovn-db with 0.0.0.0 as remote address, although in kolla-ansible we are using a `api_interface_address` ip as cli remote, which will make conflict in ovn logs if used, for example:\nuse 192.168.1.20-192.168.1.23 as `api_interface_address` of kolla-ansible in controller nodes, then deploy kolla-ansible and create ovn cluster, you definitely are going to see an error log like this:\novsdb_jsonrpc_server|ERR|ptcp:6641:0.0.0.0: listen\nfailed: Address already in use\n\nI guess best solution for Now will be to remove cli remotes and deprecate them, what will change? almost nothing, some error logs will be removed.","commit_id":"3324b3b8d679c6993586536c2ce422281c113cb8"}]}