{"action":"opened","issue":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/24864","repository_url":"https://api.github.com/repos/kubernetes/kubernetes","labels_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/24864/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/24864/comments","events_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/24864/events","html_url":"https://github.com/kubernetes/kubernetes/issues/24864","id":151398908,"number":24864,"title":"Attached PDE in GCE fails with FQDN as the node name","user":{"login":"cmoad","id":581272,"avatar_url":"https://avatars.githubusercontent.com/u/581272?v=3","gravatar_id":"","url":"https://api.github.com/users/cmoad","html_url":"https://github.com/cmoad","followers_url":"https://api.github.com/users/cmoad/followers","following_url":"https://api.github.com/users/cmoad/following{/other_user}","gists_url":"https://api.github.com/users/cmoad/gists{/gist_id}","starred_url":"https://api.github.com/users/cmoad/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cmoad/subscriptions","organizations_url":"https://api.github.com/users/cmoad/orgs","repos_url":"https://api.github.com/users/cmoad/repos","events_url":"https://api.github.com/users/cmoad/events{/privacy}","received_events_url":"https://api.github.com/users/cmoad/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-04-27T14:23:13Z","updated_at":"2016-04-27T14:23:13Z","closed_at":null,"body":"Using v1.2.3 we are getting the following error with the default name of the node as registered by the kubelet.\r\n\r\n```\r\n989350    2417 gce_util.go:187] Error attaching PD \"sinopia-e1b\": googleapi: Error 400: Invalid value 'k8s-node-frontend03.c.geofeedia-qa1.internal'. Values must match the following\r\n989561    2417 gce_util.go:183] Retrying attach for GCE PD \"sinopia-e1b\" (retry count=3).\r\n```\r\n\r\nWe are able to get around the issue by explicitly running the kubelet with `--hostname-override=$(hostname -s)` but this issue could trip up others and it would be nice to avoid the workaround."}}