)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":26285,"name":"wu.chunyang","email":"wchy1001@gmail.com","username":"wu.chunyang"},"change_message_id":"a52a0e43cbfa371c1c5413c997708f4c1293a390","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"31bcc2dd_4fdf5dbb","updated":"2023-12-11 02:29:27.000000000","message":"HI: Bo\u0026hirotaka,  Are you familiar with IPv6? our CI encounters an error randomly： docker daemon failed to set ipv6 route due to the file exists ERROR. after a investigation，i found the route may be already configured by the RA protocol for slaac subnet.So in this commit, i don\u0027t set the ipv6 route for slaac or dhcpv6-statless subnet to prevent  t this error. in my test environment, when I disable route, i got a new route: `default via fe80::f816:3eff:feff:9783 dev eth0 proto ra metric 1024 expires 215sec hoplimit 64 pref medium`, It seems to be generated by the RA protocal which is our expected. however, I am not an expert on IPV6, so I am not sure whether there is a better solution to fix this?","commit_id":"21b4cc2cf7ca3a09bdefb3654dcbb07043ea2ee6"},{"author":{"_account_id":28691,"name":"Bo Tran","email":"ministry.96.nd@gmail.com","username":"ministry"},"change_message_id":"7af72885161779eb9a76ad30296fdb90b7dadd94","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"45c5522e_120870e6","in_reply_to":"31bcc2dd_4fdf5dbb","updated":"2023-12-11 02:39:24.000000000","message":"I am not an expert on IPV6, but I think IPv6 being same logic about route with IPv4.\n\nThe routing rule being fetch from dhcp server. So, I think in this case, we should handle about exception when default route existed or re-write default route by to do delete default routing rule before add new.","commit_id":"21b4cc2cf7ca3a09bdefb3654dcbb07043ea2ee6"},{"author":{"_account_id":26285,"name":"wu.chunyang","email":"wchy1001@gmail.com","username":"wu.chunyang"},"change_message_id":"d2c16094db6ecaa89e971c38f1ccb83894036650","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"73fb748e_b835664c","in_reply_to":"45c5522e_120870e6","updated":"2023-12-11 06:04:24.000000000","message":"Hi, Bo, from the neutron ipv6 document, there three ways to allocate ipv6 address and routes, 1. dhcpv6-stateful which is the same as ipv4, in this case we need to handle it as the same as ipv4. 2\u00263:  dhcpv6-stateless \u0026 slaac in these subnet, nic will get ip and route from the RA(route advertisement) protocol, in this case, we still need to  configure the IP for the container, maybe due to some strict for docker network driver. but we don\u0027t need to configure the route for the container, because the route will be added by the nic in the database container via RA protocol.","commit_id":"21b4cc2cf7ca3a09bdefb3654dcbb07043ea2ee6"},{"author":{"_account_id":26285,"name":"wu.chunyang","email":"wchy1001@gmail.com","username":"wu.chunyang"},"change_message_id":"be4ab44c1202207792324137bf7455bfbc52a0f9","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"0f0be16f_dc3637be","in_reply_to":"73fb748e_b835664c","updated":"2023-12-11 06:12:49.000000000","message":"As we are all not familiar with the IPV6, so I\u0027ll merge this commit to fix the CI.","commit_id":"21b4cc2cf7ca3a09bdefb3654dcbb07043ea2ee6"}]}