)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":8898,"name":"Chris Wedgwood","email":"cw@f00f.org","username":"anticw"},"change_message_id":"16bd84bb8ecdab924a709476fcdffb79f78c9c6d","unresolved":false,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Ubuntu 18.04, disable systemd-resolved"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Updated k8s deploy script to disable systemd-resolved service for ubuntu bionic."},{"line_number":10,"context_line":"This to avoid interference between the system-resolved\u0027s local dns cache stub"},{"line_number":11,"context_line":"and the coredns, both running on port 53."},{"line_number":12,"context_line":"This solution will rely on the static /etc/resolv.conf file for name resolution,"},{"line_number":13,"context_line":"instead of using the systemd-resolved service and its local stub dns."},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"Change-Id: I1eb54d9ec70cebe89c5d92e06b387a5ef358ef00"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":3,"id":"3fa7e38b_5ee5bc3c","line":13,"range":{"start_line":9,"start_character":2,"end_line":13,"end_character":7},"updated":"2020-01-29 21:00:04.000000000","message":"could reflow that if you get a chance to \u003c\u003d 75 cols","commit_id":"373b230b36421ff4d09e3798216c83197fa032cd"}],"tools/deployment/common/005-deploy-k8s.sh":[{"author":{"_account_id":17591,"name":"Steve Wilkerson","email":"wilkers.steve@gmail.com","username":"srwilkers"},"change_message_id":"c786b79f4b1ce2f5f61813293c406ede9895e69c","unresolved":false,"context_lines":[{"line_number":45,"context_line":"  # kubelet to resolve cluster services."},{"line_number":46,"context_line":"  sudo mv /etc/resolv.conf /etc/resolv.conf.backup"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"  # Create symbolic link to the resolv.conf file managed by systemd-resolved, as"},{"line_number":49,"context_line":"  # the kubelet.resolv-conf extra-config flag is automatically executed by the"},{"line_number":50,"context_line":"  # minikube start command, regardless of being passed in here"},{"line_number":51,"context_line":"  sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf"},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"  sudo bash -c \"echo \u0027nameserver 10.96.0.10\u0027 \u003e\u003e /etc/resolv.conf\""},{"line_number":54,"context_line":""}],"source_content_type":"text/x-sh","patch_set":2,"id":"3fa7e38b_0dc72067","line":51,"range":{"start_line":48,"start_character":0,"end_line":51,"end_character":62},"updated":"2020-01-29 18:03:01.000000000","message":"Note this comment and the actual generation of the flag by minikube here: https://zuul.opendev.org/t/openstack/build/e22ebe6efa06490a88ec990b13a79f60/log/job-output.txt#1007","commit_id":"46f8d5991e17ce72baa63a2b339087e7b8891637"},{"author":{"_account_id":28664,"name":"Ahmad Mahmoudi","email":"ahmad.mahmoudi@att.com","username":"ahmad"},"change_message_id":"c59fdb08024831054f1fbc9111923ded9b0e2ed4","unresolved":false,"context_lines":[{"line_number":45,"context_line":"  # kubelet to resolve cluster services."},{"line_number":46,"context_line":"  sudo mv /etc/resolv.conf /etc/resolv.conf.backup"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"  # Create symbolic link to the resolv.conf file managed by systemd-resolved, as"},{"line_number":49,"context_line":"  # the kubelet.resolv-conf extra-config flag is automatically executed by the"},{"line_number":50,"context_line":"  # minikube start command, regardless of being passed in here"},{"line_number":51,"context_line":"  sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf"},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"  sudo bash -c \"echo \u0027nameserver 10.96.0.10\u0027 \u003e\u003e /etc/resolv.conf\""},{"line_number":54,"context_line":""}],"source_content_type":"text/x-sh","patch_set":2,"id":"3fa7e38b_a8891a70","line":51,"range":{"start_line":48,"start_character":0,"end_line":51,"end_character":62},"in_reply_to":"3fa7e38b_0dc72067","updated":"2020-01-29 18:53:36.000000000","message":"Steve, if we use the systemd.resolved service, then the contents of /etc/resolv.conf will be dictated by the systemd.resolved local cached stub dns /etc/systemd/resolve/resolv.conf, which only contains 127.0.0.1:53\nAnd any manual update of the /etc/resolv.conf will be irrelevant.\nThe problem is that the systemd-resolved stub dns is running locally on port 53 and so is the cluster dns.\nQuestion is in ubuntu 18.04 should we use systemd-resolved service, or should we disable systemd-resolved service, and rely on statically configured /etc/resolv.conf instead for name resolution.","commit_id":"46f8d5991e17ce72baa63a2b339087e7b8891637"},{"author":{"_account_id":28664,"name":"Ahmad Mahmoudi","email":"ahmad.mahmoudi@att.com","username":"ahmad"},"change_message_id":"f57613c1fdede3dc02d96660915eaebe50ffff89","unresolved":false,"context_lines":[{"line_number":45,"context_line":"  # kubelet to resolve cluster services."},{"line_number":46,"context_line":"  sudo mv /etc/resolv.conf /etc/resolv.conf.backup"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"  # Create symbolic link to the resolv.conf file managed by systemd-resolved, as"},{"line_number":49,"context_line":"  # the kubelet.resolv-conf extra-config flag is automatically executed by the"},{"line_number":50,"context_line":"  # minikube start command, regardless of being passed in here"},{"line_number":51,"context_line":"  sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf"},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"  sudo bash -c \"echo \u0027nameserver 10.96.0.10\u0027 \u003e\u003e /etc/resolv.conf\""},{"line_number":54,"context_line":""}],"source_content_type":"text/x-sh","patch_set":2,"id":"3fa7e38b_cdd7c8bc","line":51,"range":{"start_line":48,"start_character":0,"end_line":51,"end_character":62},"in_reply_to":"3fa7e38b_0dc72067","updated":"2020-01-29 18:22:33.000000000","message":"good catch! I thought I had removed this line. Must have been added as part of a rebase. I will remove this line. there should not be a soft link to /etc/resolv.conf.\nThanks.","commit_id":"46f8d5991e17ce72baa63a2b339087e7b8891637"},{"author":{"_account_id":17591,"name":"Steve Wilkerson","email":"wilkers.steve@gmail.com","username":"srwilkers"},"change_message_id":"b70bf9ca15153af03c5e5f57682c35f10f957f69","unresolved":false,"context_lines":[{"line_number":45,"context_line":"  # kubelet to resolve cluster services."},{"line_number":46,"context_line":"  sudo mv /etc/resolv.conf /etc/resolv.conf.backup"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"  # Create symbolic link to the resolv.conf file managed by systemd-resolved, as"},{"line_number":49,"context_line":"  # the kubelet.resolv-conf extra-config flag is automatically executed by the"},{"line_number":50,"context_line":"  # minikube start command, regardless of being passed in here"},{"line_number":51,"context_line":"  sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf"},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"  sudo bash -c \"echo \u0027nameserver 10.96.0.10\u0027 \u003e\u003e /etc/resolv.conf\""},{"line_number":54,"context_line":""}],"source_content_type":"text/x-sh","patch_set":2,"id":"3fa7e38b_c86016a1","line":51,"range":{"start_line":48,"start_character":0,"end_line":51,"end_character":62},"in_reply_to":"3fa7e38b_a8891a70","updated":"2020-01-29 19:08:19.000000000","message":"I understand what you\u0027re saying - I did the work here to work around the move to systemd-resolved in 18.04.  The point is: even with what you\u0027re doing here, Minikube is still going to direct the kubelet to use /run/systemd/resolve/resolv.conf for dns configuration, no matter what you do.  This is built into the Minikube binary and will not change, full stop.  My question has been:  how do you plan to circumvent this?  I\u0027m looking at other job runs in this repository, and I\u0027m not seeing any issues with conflicts or failure in DNS resolution.  What exactly is this change fixing?","commit_id":"46f8d5991e17ce72baa63a2b339087e7b8891637"},{"author":{"_account_id":28664,"name":"Ahmad Mahmoudi","email":"ahmad.mahmoudi@att.com","username":"ahmad"},"change_message_id":"d033029245492adf7c9ed7a28799f8196ae6b5d8","unresolved":false,"context_lines":[{"line_number":45,"context_line":"  # kubelet to resolve cluster services."},{"line_number":46,"context_line":"  sudo mv /etc/resolv.conf /etc/resolv.conf.backup"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"  # Create symbolic link to the resolv.conf file managed by systemd-resolved, as"},{"line_number":49,"context_line":"  # the kubelet.resolv-conf extra-config flag is automatically executed by the"},{"line_number":50,"context_line":"  # minikube start command, regardless of being passed in here"},{"line_number":51,"context_line":"  sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf"},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"  sudo bash -c \"echo \u0027nameserver 10.96.0.10\u0027 \u003e\u003e /etc/resolv.conf\""},{"line_number":54,"context_line":""}],"source_content_type":"text/x-sh","patch_set":2,"id":"3fa7e38b_83751f99","line":51,"range":{"start_line":48,"start_character":0,"end_line":51,"end_character":62},"in_reply_to":"3fa7e38b_c86016a1","updated":"2020-01-29 19:48:17.000000000","message":"If there use of systemd-resolved service and configuration for name resolution and there is no way around it. I don\u0027t think this ps fixes anything, and I can abandon it.\nI was using an older version of openstack-helm-infra to build the shipyard docker image, using bionic base image, the airskiff deployment failed on name resolution. I think now if I use your ps https://review.opendev.org/#/c/685775/ it should address my problem.\nAlso, not related to this, in Airship in a bottle deployment, I noticed that coredns pods are fails, because if we use systemd-resolved service is starts a local stub dns on the node listening on :53, which blocks any other dns service on that node, causing coredns/cluster-dns to fail due to port busy.","commit_id":"46f8d5991e17ce72baa63a2b339087e7b8891637"},{"author":{"_account_id":17591,"name":"Steve Wilkerson","email":"wilkers.steve@gmail.com","username":"srwilkers"},"change_message_id":"2f2bd74616dcb752d934241a55f7c7b7dc7e89f1","unresolved":false,"context_lines":[{"line_number":45,"context_line":"  # kubelet to resolve cluster services."},{"line_number":46,"context_line":"  sudo mv /etc/resolv.conf /etc/resolv.conf.backup"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"  # Create symbolic link to the resolv.conf file managed by systemd-resolved, as"},{"line_number":49,"context_line":"  # the kubelet.resolv-conf extra-config flag is automatically executed by the"},{"line_number":50,"context_line":"  # minikube start command, regardless of being passed in here"},{"line_number":51,"context_line":"  sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf"},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"  sudo bash -c \"echo \u0027nameserver 10.96.0.10\u0027 \u003e\u003e /etc/resolv.conf\""},{"line_number":54,"context_line":""}],"source_content_type":"text/x-sh","patch_set":2,"id":"3fa7e38b_88753e99","line":51,"range":{"start_line":48,"start_character":0,"end_line":51,"end_character":62},"in_reply_to":"3fa7e38b_cdd7c8bc","updated":"2020-01-29 18:46:01.000000000","message":"Well, that\u0027s not the entirety of the problem though.  Minikube will automatically pass in the path of the resolv.conf file managed by systemd-resolved, regardless of whether you disable the service or not. Please see the links I provided in my other comment. You can also see the flag on the kubelet in the systemd output as part of the post run jobs: https://zuul.opendev.org/t/openstack/build/e22ebe6efa06490a88ec990b13a79f60/log/primary/system/systemd-cgls.txt#277","commit_id":"46f8d5991e17ce72baa63a2b339087e7b8891637"},{"author":{"_account_id":8898,"name":"Chris Wedgwood","email":"cw@f00f.org","username":"anticw"},"change_message_id":"16bd84bb8ecdab924a709476fcdffb79f78c9c6d","unresolved":false,"context_lines":[{"line_number":34,"context_line":""},{"line_number":35,"context_line":"  # For ubuntu 18.04 bionic, disable systemd-resolved service, to avoid"},{"line_number":36,"context_line":"  # interference between the coreDns and the local systemd-resolved\u0027s"},{"line_number":37,"context_line":"  # dns stub resolver, both running on port 53."},{"line_number":38,"context_line":"  if [[ \"${DISTRO_ID}\" \u003d\u003d \"Ubuntu\" \u0026\u0026 \"${DISTRO_CODENAME}\" \u003d\u003d \"bionic\" ]]; then"},{"line_number":39,"context_line":"    sudo systemctl disable systemd-resolved.service"},{"line_number":40,"context_line":"    sudo systemctl stop systemd-resolved.service"},{"line_number":41,"context_line":"    sudo systemctl mask systemd-resolved.service"}],"source_content_type":"text/x-sh","patch_set":3,"id":"3fa7e38b_1e766493","line":38,"range":{"start_line":37,"start_character":1,"end_line":38,"end_character":72},"updated":"2020-01-29 21:00:04.000000000","message":"why not test for systemd-resolved?","commit_id":"373b230b36421ff4d09e3798216c83197fa032cd"}]}