{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes-incubator/cri-o/issues/1769","repository_url":"https://api.github.com/repos/kubernetes-incubator/cri-o","labels_url":"https://api.github.com/repos/kubernetes-incubator/cri-o/issues/1769/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes-incubator/cri-o/issues/1769/comments","events_url":"https://api.github.com/repos/kubernetes-incubator/cri-o/issues/1769/events","html_url":"https://github.com/kubernetes-incubator/cri-o/issues/1769","id":356580639,"node_id":"MDU6SXNzdWUzNTY1ODA2Mzk=","number":1769,"title":"Ubuntu 18.04: DNS resolution broken after scheduling hostport enabled pods","user":{"login":"fjudith","id":17888379,"node_id":"MDQ6VXNlcjE3ODg4Mzc5","avatar_url":"https://avatars1.githubusercontent.com/u/17888379?v=4","gravatar_id":"","url":"https://api.github.com/users/fjudith","html_url":"https://github.com/fjudith","followers_url":"https://api.github.com/users/fjudith/followers","following_url":"https://api.github.com/users/fjudith/following{/other_user}","gists_url":"https://api.github.com/users/fjudith/gists{/gist_id}","starred_url":"https://api.github.com/users/fjudith/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fjudith/subscriptions","organizations_url":"https://api.github.com/users/fjudith/orgs","repos_url":"https://api.github.com/users/fjudith/repos","events_url":"https://api.github.com/users/fjudith/events{/privacy}","received_events_url":"https://api.github.com/users/fjudith/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-09-03T18:41:54Z","updated_at":"2018-09-03T20:34:11Z","closed_at":null,"author_association":"NONE","body":"<!--\r\nIf you are reporting a new issue, make sure that we do not have any duplicates\r\nalready open. You can ensure this by searching the issue list for this\r\nrepository. If there is a duplicate, please close your issue and add a comment\r\nto the existing issue instead.\r\n\r\nIf you suspect your issue is a bug, please edit your issue description to\r\ninclude the BUG REPORT INFORMATION shown below. If you fail to provide this\r\ninformation within 7 days, we cannot debug your issue and will close it. We\r\nwill, however, reopen it if you later provide the information.\r\n\r\nFor more information about reporting issues, see\r\nhttps://github.com/kubernetes-incubator/cri-o/blob/master/CONTRIBUTING.md#reporting-issues\r\n\r\n---------------------------------------------------\r\nGENERAL SUPPORT INFORMATION\r\n---------------------------------------------------\r\n\r\nThe GitHub issue tracker is for bug reports and feature requests.\r\nGeneral support for **CRI-O** can be found at the following locations:\r\n\r\n- IRC - #cri-o channel on irc.freenode.org\r\n- Slack - kubernetes.slack.com #sig-node channel\r\n- Post a question on StackOverflow, using the CRI-O tag\r\n\r\n---------------------------------------------------\r\nBUG REPORT INFORMATION\r\n---------------------------------------------------\r\nUse the commands below to provide key information from your environment:\r\nYou do NOT have to include this information if this is a FEATURE REQUEST\r\n-->\r\n\r\n**Description**\r\n\r\n<!--\r\nBriefly describe the problem you are having in a few paragraphs.\r\n-->\r\n\r\nCri-O breaks DNS resolution once pod with \"Hostport\" is scheduled.\r\nI'm logging this issue here, as i was unable to reproduce this issue on Docker 17.03 and Containerd 1.1.3/1.2.0-beta.\r\n\r\nThe symptoms are similar to https://github.com/kubernetes/kubeadm/issues/273 .\r\n\r\n**Steps to reproduce the issue:**\r\n1. Schedule a pod with `hostPort` container spec configured.\r\n2. Kubernetes shows the pod in ImagePullBack error.\r\n3. DNS resolution is not working anymore. However kubelet and crio service disabled.\r\n\r\n**Additional information you deem important (e.g. issue happens only occasionally):**\r\n\r\n**Output of `crio --version`:**\r\n\r\n`cri-o-1.11` Xenial Package \r\n\r\n\r\n**Additional environment details (AWS, VirtualBox, physical, etc.):**\r\n\r\n* Hetzner Cloud and Scaleway\r\n* OS: Ubuntu 18.04 Bionic\r\n* Kubernetes 1.11.2\r\n* CNI 0.7.1\r\n* CNI runtime: Issue observed using Canal, Cillium and Weave\r\n"},"comment":{"url":"https://api.github.com/repos/kubernetes-incubator/cri-o/issues/comments/418189378","html_url":"https://github.com/kubernetes-incubator/cri-o/issues/1769#issuecomment-418189378","issue_url":"https://api.github.com/repos/kubernetes-incubator/cri-o/issues/1769","id":418189378,"node_id":"MDEyOklzc3VlQ29tbWVudDQxODE4OTM3OA==","user":{"login":"runcom","id":849915,"node_id":"MDQ6VXNlcjg0OTkxNQ==","avatar_url":"https://avatars2.githubusercontent.com/u/849915?v=4","gravatar_id":"","url":"https://api.github.com/users/runcom","html_url":"https://github.com/runcom","followers_url":"https://api.github.com/users/runcom/followers","following_url":"https://api.github.com/users/runcom/following{/other_user}","gists_url":"https://api.github.com/users/runcom/gists{/gist_id}","starred_url":"https://api.github.com/users/runcom/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/runcom/subscriptions","organizations_url":"https://api.github.com/users/runcom/orgs","repos_url":"https://api.github.com/users/runcom/repos","events_url":"https://api.github.com/users/runcom/events{/privacy}","received_events_url":"https://api.github.com/users/runcom/received_events","type":"User","site_admin":false},"created_at":"2018-09-03T20:34:11Z","updated_at":"2018-09-03T20:34:11Z","author_association":"MEMBER","body":"> Not a cri-o problem.\r\n> Look here: kubernetes/kubernetes#66067\r\n\r\ndo you happen to know why docker and containerd are working though?"}}
{"actor":{"display_login":"runcom"}}