<p>i've looked through several solutions but couldnt find an answer, so i'm trying to run a stateful set on the cluster, but the pod fails to run because of unbound claim. I'm running <strong>t2.large</strong> machines with <strong>Bottlerocket</strong> host types.</p>
<p><strong>kubectl get events</strong></p>
<pre><code>28m         Warning   FailedScheduling         pod/carabbitmq-0                              pod has unbound immediate PersistentVolumeClaims (repeated 3 times)
28m         Normal    Scheduled                pod/carabbitmq-0                              Successfully assigned default/carabbitmq-0 to ip-x.compute.internal
28m         Normal    SuccessfulAttachVolume   pod/carabbitmq-0                              AttachVolume.Attach succeeded for volume &quot;pvc-f6e8ec20-4bc1-4539-8d11-2dd1b3dbd4d7&quot;
28m         Normal    Pulled                   pod/carabbitmq-0                              Container image &quot;busybox:1.30.1&quot; already present on machine
</code></pre>
<p><strong>kubectl get pv,pvc</strong> + describe</p>
<pre><code>NAME                                      STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
persistentvolumeclaim/data-carabbitmq-0   Bound    pvc-f6e8ec20-4bc1-4539-8d11-2dd1b3dbd4d7   30Gi       RWO            gp2            12m

NAME                                                        CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                        STORAGECLASS   REASON   AGE
persistentvolume/pvc-f6e8ec20-4bc1-4539-8d11-2dd1b3dbd4d7   30Gi       RWO            Retain           Bound    rabbitmq/data-carabbitmq-0   gp2                     12m
</code></pre>
<p>describe pv:</p>
<pre><code>Name:              pvc-f6e8ec20-4bc1-4539-8d11-2dd1b3dbd4d7
Labels:            failure-domain.beta.kubernetes.io/region=eu-west-1
                   failure-domain.beta.kubernetes.io/zone=eu-west-1b
Annotations:       kubernetes.io/createdby: aws-ebs-dynamic-provisioner
                   pv.kubernetes.io/bound-by-controller: yes
                   pv.kubernetes.io/provisioned-by: kubernetes.io/aws-ebs
Finalizers:        [kubernetes.io/pv-protection]
StorageClass:      gp2
Status:            Bound
Claim:             rabbitmq/data-carabbitmq-0
Reclaim Policy:    Retain
Access Modes:      RWO
VolumeMode:        Filesystem
Capacity:          30Gi
Node Affinity:     
  Required Terms:  
    Term 0:        failure-domain.beta.kubernetes.io/zone in [eu-west-1b]
                   failure-domain.beta.kubernetes.io/region in [eu-west-1]
Message:           
Source:
    Type:       AWSElasticBlockStore (a Persistent Disk resource in AWS)
    VolumeID:   aws://eu-west-1b/vol-xx
    FSType:     ext4
    Partition:  0
    ReadOnly:   false
Events:         &lt;none&gt;
</code></pre>
<p>describe pvc:</p>
<pre><code>Name:          data-carabbitmq-0
Namespace:     rabbitmq
StorageClass:  gp2
Status:        Bound
Volume:        pvc-f6e8ec20-4bc1-4539-8d11-2dd1b3dbd4d7
Labels:        app=rabbitmq-ha
               release=rabbit-mq
Annotations:   pv.kubernetes.io/bind-completed: yes
               pv.kubernetes.io/bound-by-controller: yes
               volume.beta.kubernetes.io/storage-provisioner: kubernetes.io/aws-ebs
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:      30Gi
Access Modes:  RWO
VolumeMode:    Filesystem
Mounted By:    carabbitmq-0
Events:
  Type    Reason                 Age   From                         Message
  ----    ------                 ----  ----                         -------
  Normal  ProvisioningSucceeded  36m   persistentvolume-controller  Successfully provisioned volume pvc-f6e8ec20-4bc1-4539-8d11-2dd1b3dbd4d7 using kubernetes.io/aws-ebs
</code></pre>
<p>The storage type is gp2.</p>
<pre><code>Name:                  gp2
IsDefaultClass:        Yes
Annotations:           storageclass.kubernetes.io/is-default-class=true
Provisioner:           kubernetes.io/aws-ebs
Parameters:            encrypted=true,type=gp2
AllowVolumeExpansion:  &lt;unset&gt;
MountOptions:
  debug
ReclaimPolicy:      Retain
VolumeBindingMode:  Immediate
Events:             &lt;none&gt;
</code></pre>
<p>I'm not sure what i'm missing, same configuration used to work until i switched to &quot;t&quot; type of EC2s</p>

ArielB
<p>So, it was weird but i had some readiness probe that failed its healthchecks, i thought that it was because the volume was not mounted well.</p>
<p>The healthcheck basically did some request to localhost, which it had issues on (not sure why) - changing to 127.0.0.1 made the check pass, and then the volume error disappeard.</p>
<p>So - if you have this weird issue (volumes were mounted, but you still get that error) - check the pod's probes.</p>
