)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"15ce43531bdb57b960ac95daaf3bf435eff955cf","unresolved":false,"context_lines":[{"line_number":4,"context_line":"Commit:     Paul Belanger \u003cpabelanger@redhat.com\u003e"},{"line_number":5,"context_line":"CommitDate: 2018-03-28 22:07:01 -0400"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Stop systemd-resolve from booting on our images"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"It seems with ubuntu-bionic, systemd-resolve boots by default. This is"},{"line_number":10,"context_line":"then overwriting our /etc/resolv.conf file with its nameserver"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"bf659307_23a8518b","line":7,"updated":"2018-03-29 05:08:00.000000000","message":"If I read the docs correctly, this patch only stops the stub resolver from starting. systemd-resolvd will still run and serve requests via API calls. So we may need to do further work if it doesn\u0027t behave like we expect it to do. In the long run, working to get systemd-resolved set up properly and use it completely instead of unbound may be the better solution.","commit_id":"a3cb356550793c5993110cd98953a1618def6e39"},{"author":{"_account_id":4162,"name":"Paul Belanger","email":"pabelanger@redhat.com","username":"pabelanger"},"change_message_id":"b898e29d2d5ca14c50ef8727e65cdffa29ff6844","unresolved":false,"context_lines":[{"line_number":4,"context_line":"Commit:     Paul Belanger \u003cpabelanger@redhat.com\u003e"},{"line_number":5,"context_line":"CommitDate: 2018-03-28 22:07:01 -0400"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Stop systemd-resolve from booting on our images"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"It seems with ubuntu-bionic, systemd-resolve boots by default. This is"},{"line_number":10,"context_line":"then overwriting our /etc/resolv.conf file with its nameserver"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"bf659307_a93afbc8","line":7,"in_reply_to":"bf659307_23a8518b","updated":"2018-03-29 12:40:05.000000000","message":"Ya, this is correct. The process does start, but doesn\u0027t listen on 127.0.0.53. We could in a follow up actually stop it from starting all together.","commit_id":"a3cb356550793c5993110cd98953a1618def6e39"}],"nodepool/elements/nodepool-base/finalise.d/89-unbound":[{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"167dd06304c2c662550b1ac31e108d94eef0fee6","unresolved":false,"context_lines":[{"line_number":168,"context_line":"EOF"},{"line_number":169,"context_line":"fi"},{"line_number":170,"context_line":""},{"line_number":171,"context_line":"# If systemd-resolved is installed, stop it from running. We want to use unbound"},{"line_number":172,"context_line":"# to manage our DNS requests."},{"line_number":173,"context_line":"if $(systemctl -q is-enabled systemd-resolved.service); then"},{"line_number":174,"context_line":"    systemctl disable systemd-resolved.service"},{"line_number":175,"context_line":"fi"},{"line_number":176,"context_line":""},{"line_number":177,"context_line":"case \"$DIB_INIT_SYSTEM\" in"},{"line_number":178,"context_line":"    upstart)"}],"source_content_type":"application/x-shellscript","patch_set":2,"id":"bf659307_579c110e","line":175,"range":{"start_line":171,"start_character":0,"end_line":175,"end_character":2},"updated":"2018-03-29 16:18:03.000000000","message":"I think this whole section should move into the systemd case of the switch below. Basically put it after line 181 and before 182.","commit_id":"c400a304bae86a1113a800193b8991da7189f0e4"}]}