{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/43468","repository_url":"https://api.github.com/repos/kubernetes/kubernetes","labels_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/43468/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/43468/comments","events_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/43468/events","html_url":"https://github.com/kubernetes/kubernetes/issues/43468","id":215842049,"number":43468,"title":"Deployment on openstack-heat fails on docker - CentOS 7 image","user":{"login":"carlosedp","id":20382,"avatar_url":"https://avatars3.githubusercontent.com/u/20382?v=3","gravatar_id":"","url":"https://api.github.com/users/carlosedp","html_url":"https://github.com/carlosedp","followers_url":"https://api.github.com/users/carlosedp/followers","following_url":"https://api.github.com/users/carlosedp/following{/other_user}","gists_url":"https://api.github.com/users/carlosedp/gists{/gist_id}","starred_url":"https://api.github.com/users/carlosedp/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/carlosedp/subscriptions","organizations_url":"https://api.github.com/users/carlosedp/orgs","repos_url":"https://api.github.com/users/carlosedp/repos","events_url":"https://api.github.com/users/carlosedp/events{/privacy}","received_events_url":"https://api.github.com/users/carlosedp/received_events","type":"User","site_admin":false},"labels":[{"id":617149945,"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/needs-sig","name":"needs-sig","color":"ededed","default":false},{"id":239914558,"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/sig/openstack","name":"sig/openstack","color":"d2b48c","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-03-21T18:49:05Z","updated_at":"2017-06-06T02:36:40Z","closed_at":null,"body":"**Kubernetes version** (use `kubectl version`): Trying to deploy 1.6.0-beta4\r\n\r\n\r\n**Environment**:\r\n- **Cloud provider or hardware configuration**: Mirantis Openstack 9.2 (Mitaka) over VMware VSphere\r\n- **OS** (e.g. from /etc/os-release):CentOS 7.3 (1611)\r\n- **Kernel** (e.g. `uname -a`): 3.10.0-514.el7.x86_64\r\n- **Install tools**: kube-up.sh from 1.6.0-beta4 release\r\n- **Others**: Deployed from a CentOS 7 machine into Openstack using the following parameters:\r\n```\r\nexport OS_TENANT_NAME='admin'\r\nexport OS_TENANT_ID=d9e0430698984610b523d448c4609490\r\nexport OS_PROJECT_NAME='admin'\r\nexport OS_USERNAME='admin'\r\nexport OS_PASSWORD='admin'\r\nexport OS_AUTH_URL='http://10.178.11.224:5000/v2.0'\r\nexport OS_DEFAULT_DOMAIN='default'\r\nexport OS_AUTH_STRATEGY='keystone'\r\nexport OS_REGION_NAME='RegionOne'\r\n\r\nexport STACK_NAME=kube-stack\r\nexport NUMBER_OF_MINIONS=2\r\nexport MAX_NUMBER_OF_MINIONS=4\r\nexport MASTER_FLAVOR=m1.medium\r\nexport MINION_FLAVOR=m1.medium\r\nexport EXTERNAL_NETWORK=admin_floating_net\r\nexport DNS_SERVER=8.8.8.8\r\nexport SWIFT_SERVER_URL=http://10.178.11.224:8080/v1/AUTH_d9e0430698984610b523d448c4609490\r\nexport ENABLE_PROXY=false\r\nexport OPENSTACK_IMAGE_NAME=CentOS-7-x86_64-GenericCloud-1611.vmdk\r\nexport IMAGE_FORMAT=vmdk\r\nexport STACK_CREATE_TIMEOUT=150\r\n```\r\n\r\n**What happened**: Deployment is not finished. Going into master and minion saw some docker errors:\r\n\r\n```\r\nMar 21 18:43:44 kube-stack-master kube-master-addons.sh[12726]: Redirecting to /bin/systemctl restart  docker.service\r\nMar 21 18:43:44 kube-stack-master systemd[1]: Starting Docker Cleanup...\r\nMar 21 18:43:44 kube-stack-master systemd[1]: Starting Docker Storage Setup...\r\nMar 21 18:43:44 kube-stack-master systemd[1]: Started Docker Cleanup.\r\nMar 21 18:43:44 kube-stack-master sh[2097]: Cannot connect to the Docker daemon. Is the docker daemon running on this host?\r\nMar 21 18:43:44 kube-stack-master docker-storage-setup[2098]: INFO: Volume group backing root filesystem could not be determined\r\nMar 21 18:43:44 kube-stack-master docker-storage-setup[2098]: ERROR: No valid volume group found. Exiting.\r\nMar 21 18:43:44 kube-stack-master systemd[1]: docker-storage-setup.service: main process exited, code=exited, status=1/FAILURE\r\nMar 21 18:43:44 kube-stack-master systemd[1]: Failed to start Docker Storage Setup.\r\nMar 21 18:43:44 kube-stack-master systemd[1]: Unit docker-storage-setup.service entered failed state.\r\nMar 21 18:43:44 kube-stack-master systemd[1]: docker-storage-setup.service failed.\r\nMar 21 18:43:44 kube-stack-master systemd[1]: Starting Docker Application Container Engine...\r\nMar 21 18:43:44 kube-stack-master dockerd-current[2124]: time=\"2017-03-21T18:43:44.218692166Z\" level=info msg=\"libcontainerd: new containerd process, pid: 2131\"\r\nMar 21 18:43:45 kube-stack-master dockerd-current[2124]: time=\"2017-03-21T18:43:45.263180412Z\" level=warning msg=\"devmapper: Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or use `man docker` to refer to dm.thinpooldev section.\"\r\nMar 21 18:43:45 kube-stack-master dockerd-current[2124]: time=\"2017-03-21T18:43:45.279969801Z\" level=warning msg=\"devmapper: Base device already exists and has filesystem xfs on it. User specified filesystem  will be ignored.\"\r\nMar 21 18:43:45 kube-stack-master dockerd-current[2124]: time=\"2017-03-21T18:43:45.296839273Z\" level=info msg=\"[graphdriver] using prior storage driver \\\"devicemapper\\\"\"\r\nMar 21 18:43:45 kube-stack-master dockerd-current[2124]: time=\"2017-03-21T18:43:45.323070349Z\" level=info msg=\"Graph migration to content-addressability took 0.00 seconds\"\r\nMar 21 18:43:45 kube-stack-master dockerd-current[2124]: time=\"2017-03-21T18:43:45.323983231Z\" level=info msg=\"Loading containers: start.\"\r\nMar 21 18:43:45 kube-stack-master dockerd-current[2124]: time=\"2017-03-21T18:43:45.416310778Z\" level=fatal msg=\"Error starting daemon: Error initializing network controller: Error creating default \\\"bridge\\\" network: bridge device with non default name cbr0 must be created manually\"\r\nMar 21 18:43:45 kube-stack-master systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE\r\nMar 21 18:43:45 kube-stack-master systemd[1]: Failed to start Docker Application Container Engine.\r\nMar 21 18:43:45 kube-stack-master kube-master-addons.sh[12726]: Job for docker.service failed because the control process exited with error code. See \"systemctl status\r\ndocker.service\" and \"journalctl -xe\" for details.\r\nMar 21 18:43:45 kube-stack-master systemd[1]: Unit docker.service entered failed state.\r\nMar 21 18:43:45 kube-stack-master systemd[1]: docker.service failed.\r\nMar 21 18:43:45 kube-stack-master systemd[1]: Starting Docker Storage Setup...\r\nMar 21 18:43:45 kube-stack-master systemd[1]: Starting Docker Cleanup...\r\nMar 21 18:43:45 kube-stack-master docker-storage-setup[2165]: INFO: Volume group backing root filesystem could not be determined\r\nMar 21 18:43:45 kube-stack-master sh[2166]: Cannot connect to the Docker daemon. Is the docker daemon running on this host?\r\nMar 21 18:43:45 kube-stack-master systemd[1]: Started Docker Cleanup.\r\nMar 21 18:43:45 kube-stack-master docker-storage-setup[2165]: ERROR: No valid volume group found. Exiting.\r\nMar 21 18:43:45 kube-stack-master systemd[1]: docker-storage-setup.service: main process exited, code=exited, status=1/FAILURE\r\nMar 21 18:43:45 kube-stack-master systemd[1]: Failed to start Docker Storage Setup.\r\nMar 21 18:43:45 kube-stack-master systemd[1]: Unit docker-storage-setup.service entered failed state.\r\nMar 21 18:43:45 kube-stack-master systemd[1]: docker-storage-setup.service failed.\r\nMar 21 18:43:45 kube-stack-master systemd[1]: Starting Docker Application Container Engine...\r\nMar 21 18:43:45 kube-stack-master dockerd-current[2191]: time=\"2017-03-21T18:43:45.483274168Z\" level=info msg=\"libcontainerd: new containerd process, pid: 2199\"\r\nMar 21 18:43:46 kube-stack-master dockerd-current[2191]: time=\"2017-03-21T18:43:46.535359895Z\" level=warning msg=\"devmapper: Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or use `man docker` to refer to dm.thinpooldev section.\"\r\nMar 21 18:43:46 kube-stack-master dockerd-current[2191]: time=\"2017-03-21T18:43:46.549667437Z\" level=warning msg=\"devmapper: Base device already exists and has filesystem xfs on it. User specified filesystem  will be ignored.\"\r\nMar 21 18:43:46 kube-stack-master dockerd-current[2191]: time=\"2017-03-21T18:43:46.562902380Z\" level=info msg=\"[graphdriver] using prior storage driver \\\"devicemapper\\\"\"\r\nMar 21 18:43:46 kube-stack-master dockerd-current[2191]: time=\"2017-03-21T18:43:46.587127787Z\" level=info msg=\"Graph migration to content-addressability took 0.00 seconds\"\r\nMar 21 18:43:46 kube-stack-master dockerd-current[2191]: time=\"2017-03-21T18:43:46.588027232Z\" level=info msg=\"Loading containers: start.\"\r\nMar 21 18:43:46 kube-stack-master dockerd-current[2191]: time=\"2017-03-21T18:43:46.690343505Z\" level=fatal msg=\"Error starting daemon: Error initializing network controller: Error creating default \\\"bridge\\\" network: bridge device with non default name cbr0 must be created manually\"\r\nMar 21 18:43:46 kube-stack-master systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE\r\nMar 21 18:43:46 kube-stack-master systemd[1]: Failed to start Docker Application Container Engine.\r\nMar 21 18:43:46 kube-stack-master systemd[1]: Unit docker.service entered failed state.\r\nMar 21 18:43:46 kube-stack-master systemd[1]: docker.service failed.\r\nMar 21 18:43:46 kube-stack-master kube-master-addons.sh[12726]: Job for docker.service failed because the control process exited with error code. See \"systemctl status\r\ndocker.service\" and \"journalctl -xe\" for details. \r\n```\r\n\r\n**What you expected to happen**: Deploy to finish correctly\r\n\r\n\r\n**How to reproduce it** (as minimally and precisely as possible): I just uploaded CentOS7 image into Glance, downloaded 1.6.0-beta4 tar.gz from releases, set the environment variables above and ran `KUBERNETES_PROVIDER=openstack-heat ./cluster/kube-up.sh`\r\n\r\n\r\n**Anything else we need to know**:\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/comments/306365078","html_url":"https://github.com/kubernetes/kubernetes/issues/43468#issuecomment-306365078","issue_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/43468","id":306365078,"user":{"login":"dims","id":23304,"avatar_url":"https://avatars1.githubusercontent.com/u/23304?v=3","gravatar_id":"","url":"https://api.github.com/users/dims","html_url":"https://github.com/dims","followers_url":"https://api.github.com/users/dims/followers","following_url":"https://api.github.com/users/dims/following{/other_user}","gists_url":"https://api.github.com/users/dims/gists{/gist_id}","starred_url":"https://api.github.com/users/dims/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dims/subscriptions","organizations_url":"https://api.github.com/users/dims/orgs","repos_url":"https://api.github.com/users/dims/repos","events_url":"https://api.github.com/users/dims/events{/privacy}","received_events_url":"https://api.github.com/users/dims/received_events","type":"User","site_admin":false},"created_at":"2017-06-06T02:36:39Z","updated_at":"2017-06-06T02:36:39Z","body":"/sig openstack"}}
{"actor":{"display_login":"dims"}}