{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/11011","labels_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/11011/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/11011/comments","events_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/11011/events","html_url":"https://github.com/kubernetes/kubernetes/issues/11011","id":94131949,"number":11011,"title":"AWS EBS Attaches but Pod Remains at Pending","user":{"login":"delianides","id":111170,"avatar_url":"https://avatars.githubusercontent.com/u/111170?v=3","gravatar_id":"","url":"https://api.github.com/users/delianides","html_url":"https://github.com/delianides","followers_url":"https://api.github.com/users/delianides/followers","following_url":"https://api.github.com/users/delianides/following{/other_user}","gists_url":"https://api.github.com/users/delianides/gists{/gist_id}","starred_url":"https://api.github.com/users/delianides/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/delianides/subscriptions","organizations_url":"https://api.github.com/users/delianides/orgs","repos_url":"https://api.github.com/users/delianides/repos","events_url":"https://api.github.com/users/delianides/events{/privacy}","received_events_url":"https://api.github.com/users/delianides/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/area/os/coreos","name":"area/os/coreos","color":"d4c5f9"},{"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/area/platform/aws","name":"area/platform/aws","color":"d4c5f9"},{"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/priority/P1","name":"priority/P1","color":"eb6420"},{"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/team/cluster","name":"team/cluster","color":"d2b48c"},{"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/team/community","name":"team/community","color":"d2b48c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":17,"created_at":"2015-07-09T19:24:28Z","updated_at":"2015-09-05T13:06:39Z","closed_at":null,"body":"Running the default cluster setup on AWS and using CoreOS. Creating a mongo pod with no volume is successful. But creating a pod with an attached EBS volume is not. The volume does successfully attach to the correct node but the pod remains at the pending state. \r\n\r\n```\r\nName:                           mongo\r\nNamespace:                      default\r\nImage(s):                       mongo:latest\r\nNode:                           ip-172-20-0-194.ec2.internal/172.20.0.194\r\nLabels:                         name=mongo,role=mongo\r\nStatus:                         Pending\r\nReason:\r\nMessage:\r\nIP:\r\nReplication Controllers:        <none>\r\nContainers:\r\n  mongo:\r\n    Image:      mongo:latest\r\n    Limits:\r\n      cpu:              100m\r\n    State:              Waiting\r\n      Reason:           Image: mongo:latest is not ready on the node\r\n    Ready:              False\r\n    Restart Count:      0\r\nConditions:\r\n  Type          Status\r\n  Ready         False\r\nEvents:\r\n  FirstSeen                             LastSeen                        Count   From                                    SubobjectPath   Reason          Message\r\n  Thu, 09 Jul 2015 15:05:08 -0400       Thu, 09 Jul 2015 15:05:08 -0400 1       {scheduler }                                            scheduled       Successfully assigned mongo to ip-172-20-0-194.ec2.internal\r\n  Thu, 09 Jul 2015 15:05:14 -0400       Thu, 09 Jul 2015 15:13:28 -0400 51      {kubelet ip-172-20-0-194.ec2.internal}                  failedMount     Unable to mount volumes for pod \"mongo_default\": fork/exec /usr/share/google/safe_format_and_mount: no such file or directory\r\n  Thu, 09 Jul 2015 15:05:14 -0400       Thu, 09 Jul 2015 15:13:28 -0400 51      {kubelet ip-172-20-0-194.ec2.internal}                  failedSync      Error syncing pod, skipping: fork/exec /usr/share/google/safe_format_and_mount: no such file or directory\r\n```\r\n\r\nThe template file: \r\n\r\n```\r\nkind: Pod\r\napiVersion: v1\r\nmetadata:\r\n  name: mongo\r\n  labels:\r\n    name: mongo\r\n    role: mongo\r\nspec:\r\n  containers:\r\n  - name: mongo\r\n    image: mongo:latest\r\n    ports:\r\n    - name: mongo\r\n      containerPort: 27017\r\n      protocol: TCP\r\n    resources: {}\r\n    volumeMounts:\r\n    - mountPath: /data/db\r\n      name: mongo-disk\r\n  volumes:\r\n  - name: mongo-disk\r\n    awsElasticBlockStore:\r\n      volumeID: vol-xxxxxxx # PR#10181\r\n      fsType: ext4\r\n```\r\n\r\nFollowed new `VolumeID` name per #10181. There are no helpful error messages on the kubelet or controller-manager. I moved up to use larger ec2 instances rather than the default t2.micro and didn't have any change.\r\n"},"comment":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/comments/137952582","html_url":"https://github.com/kubernetes/kubernetes/issues/11011#issuecomment-137952582","issue_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/11011","id":137952582,"user":{"login":"bliss","id":73997,"avatar_url":"https://avatars.githubusercontent.com/u/73997?v=3","gravatar_id":"","url":"https://api.github.com/users/bliss","html_url":"https://github.com/bliss","followers_url":"https://api.github.com/users/bliss/followers","following_url":"https://api.github.com/users/bliss/following{/other_user}","gists_url":"https://api.github.com/users/bliss/gists{/gist_id}","starred_url":"https://api.github.com/users/bliss/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bliss/subscriptions","organizations_url":"https://api.github.com/users/bliss/orgs","repos_url":"https://api.github.com/users/bliss/repos","events_url":"https://api.github.com/users/bliss/events{/privacy}","received_events_url":"https://api.github.com/users/bliss/received_events","type":"User","site_admin":false},"created_at":"2015-09-05T13:06:39Z","updated_at":"2015-09-05T13:06:39Z","body":"Good day! It's still all about AWS persistent drives. I found out that say for mariadb containers persistent drive mountpoints has improper context. It prevents mariadb from reading to the drive and makes it crush. As for safe_format_and_mount script I make a workaround with solves the issue:\r\n```\r\nMOUNT_OPTIONS=\"discard,defaults,context=system_u:object_r:cgroup_t:s0\"\r\n```\r\nBut what about the issue when the script functionality gets built-in?"}}