{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/51271","repository_url":"https://api.github.com/repos/kubernetes/kubernetes","labels_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/51271/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/51271/comments","events_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/51271/events","html_url":"https://github.com/kubernetes/kubernetes/issues/51271","id":252625033,"node_id":"MDU6SXNzdWUyNTI2MjUwMzM=","number":51271,"title":"Service controller trying to remove all subnets for AWS LoadBalancer","user":{"login":"pingles","id":1150,"node_id":"MDQ6VXNlcjExNTA=","avatar_url":"https://avatars0.githubusercontent.com/u/1150?v=4","gravatar_id":"","url":"https://api.github.com/users/pingles","html_url":"https://github.com/pingles","followers_url":"https://api.github.com/users/pingles/followers","following_url":"https://api.github.com/users/pingles/following{/other_user}","gists_url":"https://api.github.com/users/pingles/gists{/gist_id}","starred_url":"https://api.github.com/users/pingles/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pingles/subscriptions","organizations_url":"https://api.github.com/users/pingles/orgs","repos_url":"https://api.github.com/users/pingles/repos","events_url":"https://api.github.com/users/pingles/events{/privacy}","received_events_url":"https://api.github.com/users/pingles/received_events","type":"User","site_admin":false},"labels":[{"id":105146071,"node_id":"MDU6TGFiZWwxMDUxNDYwNzE=","url":"https://api.github.com/repos/kubernetes/kubernetes/labels/kind/bug","name":"kind/bug","color":"e11d21","default":false},{"id":778118404,"node_id":"MDU6TGFiZWw3NzgxMTg0MDQ=","url":"https://api.github.com/repos/kubernetes/kubernetes/labels/lifecycle/stale","name":"lifecycle/stale","color":"795548","default":false},{"id":328487998,"node_id":"MDU6TGFiZWwzMjg0ODc5OTg=","url":"https://api.github.com/repos/kubernetes/kubernetes/labels/sig/aws","name":"sig/aws","color":"d2b48c","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":13,"created_at":"2017-08-24T14:43:40Z","updated_at":"2018-12-29T11:59:22Z","closed_at":null,"author_association":"NONE","body":"/kind bug\r\n\r\n**What happened**:\r\nWe've had a LoadBalancer service defined for a while that sits in front of a set of pods running the nginx ingress controller. I've noticed that for a while we've got events recording it trying to create a load-balancer (when one already exists) and failing as it attempts to \"detach all subnets\".\r\n\r\nThe service was created around a month ago, no changes have been made recently but 13 days ago is the first instance of it trying to create a new load balancer.\r\n\r\nDescribing the service yields the following:\r\n\r\n```\r\nName:\t\t\tnginx-ingress-svc-internal\r\nNamespace:\t\tkube-system\r\nLabels:\t\t\t<none>\r\nAnnotations:\t\tkubectl.kubernetes.io/last-applied-configuration={\"apiVersion\":\"v1\",\"kind\":\"Service\",\"metadata\":{\"annotations\":{\"service.beta.kubernetes.io/aws-load-balancer-backend-protocol\":\"http\",\"service.beta.kub...\r\n\t\t\tservice.beta.kubernetes.io/aws-load-balancer-backend-protocol=http\r\n\t\t\tservice.beta.kubernetes.io/aws-load-balancer-internal=0.0.0.0/0\r\n\t\t\tservice.beta.kubernetes.io/aws-load-balancer-ssl-cert=arn:aws:acm:eu-west-1:xxxx:certificate/xxxxxxxx\r\n\t\t\tservice.beta.kubernetes.io/aws-load-balancer-ssl-ports=https\r\nSelector:\t\tname=nginx-ingress-lb-internal\r\nType:\t\t\tLoadBalancer\r\nIP:\t\t\t100.64.226.145\r\nLoadBalancer Ingress:\tinternal-xxxxxx.eu-west-1.elb.amazonaws.com\r\nPort:\t\t\thttp\t80/TCP\r\nNodePort:\t\thttp\t31560/TCP\r\nEndpoints:\t\t192.168.114.90:80,192.168.23.28:80,192.168.27.16:80 + 7 more...\r\nPort:\t\t\thttps\t443/TCP\r\nNodePort:\t\thttps\t31631/TCP\r\nEndpoints:\t\t192.168.114.90:80,192.168.23.28:80,192.168.27.16:80 + 7 more...\r\nSession Affinity:\tNone\r\nEvents:\r\n  FirstSeen\tLastSeen\tCount\tFrom\t\t\tSubObjectPath\tType\t\tReason\t\t\t\tMessage\r\n  ---------\t--------\t-----\t----\t\t\t-------------\t--------\t------\t\t\t\t-------\r\n  13d\t\t10m\t\t186\tservice-controller\t\t\tNormal\t\tUpdatedLoadBalancer\t\tUpdated load balancer with new hosts\r\n  13d\t\t2m\t\t4026\tservice-controller\t\t\tNormal\t\tCreatingLoadBalancer\t\tCreating load balancer\r\n  13d\t\t2m\t\t4017\tservice-controller\t\t\tWarning\t\tCreatingLoadBalancerFailed\t(combined from similar events): Error creating load balancer (will retry): Failed to create load balancer for service kube-system/nginx-ingress-svc-internal: error detaching AWS loadbalancer from subnets: InvalidConfigurationRequest: Requested configuration change for LoadBalancer \"xxxxxxxx\" is invalid because you attempted to detach all the subnets for this LoadBalancer and a LoadBalancer cannot be attached to zero subnets in VPC.\r\n\t\tstatus code: 409, request id: xxxxxxx\r\n```\r\n\r\n**What you expected to happen**:\r\nI would expect no messages in the events about creating a load-balancer.\r\n\r\n**How to reproduce it (as minimally and precisely as possible)**:\r\nI'm afraid I have no idea as we've had it running without issue and only noticed the event messages by accident.\r\n\r\n**Anything else we need to know?**:\r\nIt doesn't appear to impact us as the configuration for the load-balancer is correctly associated against all nodes in the cluster. The ELB also appears to have the right tags associated:\r\n\r\n```\r\nkubernetes.io/service-name: kube-system/nginx-ingress-svc-internal\r\nKubernetesCluster: foo.x.x\r\n```\r\n\r\n**Environment**:\r\n- Kubernetes version (use `kubectl version`):\r\n```Client Version: version.Info{Major:\"1\", Minor:\"7\", GitVersion:\"v1.7.3\", GitCommit:\"2c2fe6e8278a5db2d15a013987b53968c743f2a1\", GitTreeState:\"clean\", BuildDate:\"2017-08-03T07:00:21Z\", GoVersion:\"go1.8.3\", Compiler:\"gc\", Platform:\"darwin/amd64\"}\r\nServer Version: version.Info{Major:\"1\", Minor:\"7\", GitVersion:\"v1.7.0+coreos.0\", GitCommit:\"8c1bf133b4129042ef8f7d1ffac1be14ee83ed10\", GitTreeState:\"clean\", BuildDate:\"2017-06-30T17:46:00Z\", GoVersion:\"go1.8.3\", Compiler:\"gc\", Platform:\"linux/amd64\"}\r\n```\r\n- Cloud provider or hardware configuration**:\r\nAWS VPC, CoreOS Container Linux Stable 1409.5.0.\r\n- OS (e.g. from /etc/os-release):\r\n```NAME=\"Container Linux by CoreOS\"\r\nID=coreos\r\nVERSION=1409.5.0\r\nVERSION_ID=1409.5.0\r\nBUILD_ID=2017-06-22-2222\r\nPRETTY_NAME=\"Container Linux by CoreOS 1409.5.0 (Ladybug)\"\r\nANSI_COLOR=\"38;5;75\"\r\nHOME_URL=\"https://coreos.com/\"\r\nBUG_REPORT_URL=\"https://issues.coreos.com\"\r\nCOREOS_BOARD=\"amd64-usr\"\r\n```\r\n- Kernel (e.g. `uname -a`):\r\n```Linux ip-172-19-12-176 4.11.6-coreos-r1 #1 SMP Thu Jun 22 22:04:38 UTC 2017 x86_64 Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz GenuineIntel GNU/Linux```\r\n- Install tools:\r\n- Others:\r\n"},"comment":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/comments/450487815","html_url":"https://github.com/kubernetes/kubernetes/issues/51271#issuecomment-450487815","issue_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/51271","id":450487815,"node_id":"MDEyOklzc3VlQ29tbWVudDQ1MDQ4NzgxNQ==","user":{"login":"fejta-bot","id":30488982,"node_id":"MDQ6VXNlcjMwNDg4OTgy","avatar_url":"https://avatars1.githubusercontent.com/u/30488982?v=4","gravatar_id":"","url":"https://api.github.com/users/fejta-bot","html_url":"https://github.com/fejta-bot","followers_url":"https://api.github.com/users/fejta-bot/followers","following_url":"https://api.github.com/users/fejta-bot/following{/other_user}","gists_url":"https://api.github.com/users/fejta-bot/gists{/gist_id}","starred_url":"https://api.github.com/users/fejta-bot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fejta-bot/subscriptions","organizations_url":"https://api.github.com/users/fejta-bot/orgs","repos_url":"https://api.github.com/users/fejta-bot/repos","events_url":"https://api.github.com/users/fejta-bot/events{/privacy}","received_events_url":"https://api.github.com/users/fejta-bot/received_events","type":"User","site_admin":false},"created_at":"2018-12-29T11:59:22Z","updated_at":"2018-12-29T11:59:22Z","author_association":"NONE","body":"Stale issues rot after 30d of inactivity.\nMark the issue as fresh with `/remove-lifecycle rotten`.\nRotten issues close after an additional 30d of inactivity.\n\nIf this issue is safe to close now please do so with `/close`.\n\nSend feedback to sig-testing, kubernetes/test-infra and/or [fejta](https://github.com/fejta).\n/lifecycle rotten"}}
{"actor":{"display_login":"fejta-bot"}}