)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":15197,"name":"Pierre Riteau","email":"pierre@stackhpc.com","username":"priteau","status":"StackHPC"},"change_message_id":"558702cec3ae9c120b393ad070380264c0488023","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"ba9a2ad9_ab50b9b9","updated":"2022-01-27 13:37:40.000000000","message":"\u003e Patch Set 2: Workflow-1\n\u003e \n\u003e \u003e As docker is also managing the firewall, i.e we aren\u0027t using:\n\u003e  \u003e \n\u003e  \u003e Prevent Docker from manipulating iptables\n\u003e  \u003e To prevent Docker from manipulating the iptables policies at all,\n\u003e  \u003e set the iptables key to false in /etc/docker/daemon.json. This is\n\u003e  \u003e inappropriate for most users, because the iptables policies then\n\u003e  \u003e need to be managed by hand\n\u003e  \u003e \n\u003e  \u003e Could this cause any issues when you persist some its rules?\n\u003e \n\u003e It\u0027s a good point. I\u0027ll rethink.\n\nI think we are disabling iptables management by Docker now, so we should be fine?","commit_id":"9a6942865c25b65e55bc220c6c65cd08bb65ec74"}],"releasenotes/notes/persist-seed-snat-9e97267e22249c71.yaml":[{"author":{"_account_id":15197,"name":"Pierre Riteau","email":"pierre@stackhpc.com","username":"priteau","status":"StackHPC"},"change_message_id":"c8989a55d49d9e569aeaaf8207e47882122d9982","unresolved":true,"context_lines":[{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    Fixes an issue with SNAT IPTables rules on the seed which were not"},{"line_number":5,"context_line":"    persistent, so would be absent following a reboot. This could lead to"},{"line_number":6,"context_line":"    connecitivity issues following provisioning of control plane hosts. See"},{"line_number":7,"context_line":"    `story 2006487 \u003chttps://storyboard.openstack.org/#!/story/2006487\u003e`__ for"},{"line_number":8,"context_line":"    details."}],"source_content_type":"text/x-yaml","patch_set":2,"id":"761d3b43_ee3d9e37","line":6,"range":{"start_line":6,"start_character":4,"end_line":6,"end_character":17},"updated":"2021-07-22 12:23:46.000000000","message":"connectivity","commit_id":"d5ed4852ff73557c62804e65c31afd4ea52ea668"},{"author":{"_account_id":15197,"name":"Pierre Riteau","email":"pierre@stackhpc.com","username":"priteau","status":"StackHPC"},"change_message_id":"04e5f6146587867bdbc940a97d27f46b1271dd06","unresolved":false,"context_lines":[{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    Fixes an issue with SNAT IPTables rules on the seed which were not"},{"line_number":5,"context_line":"    persistent, so would be absent following a reboot. This could lead to"},{"line_number":6,"context_line":"    connecitivity issues following provisioning of control plane hosts. See"},{"line_number":7,"context_line":"    `story 2006487 \u003chttps://storyboard.openstack.org/#!/story/2006487\u003e`__ for"},{"line_number":8,"context_line":"    details."}],"source_content_type":"text/x-yaml","patch_set":2,"id":"0aa679de_4bd84047","line":6,"range":{"start_line":6,"start_character":4,"end_line":6,"end_character":17},"in_reply_to":"761d3b43_ee3d9e37","updated":"2022-01-27 13:37:48.000000000","message":"Done","commit_id":"d5ed4852ff73557c62804e65c31afd4ea52ea668"}]}