You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Denis Krivenko (Jira)" <ji...@apache.org> on 2025/07/06 20:50:00 UTC

[jira] [Created] (HDDS-13397) S3 and HttpFS gateways are failing on deployment from Kubernetes resource examples

Denis Krivenko created HDDS-13397:
-------------------------------------

             Summary: S3 and HttpFS gateways are failing on deployment from Kubernetes resource examples
                 Key: HDDS-13397
                 URL: https://issues.apache.org/jira/browse/HDDS-13397
             Project: Apache Ozone
          Issue Type: Bug
          Components: HttpFS GateWay, kubernetes, s3gateway
    Affects Versions: 2.0.0
            Reporter: Denis Krivenko


Ozone 2.0 cannot be successfully deployed to Kubernetes using provided resource examples because of constantly failing liveness probes.

How to reproduce:
 # Deploy Ozone 2.0 from `kubernetes/examples/minikube`

 
{code:java}
ozone-2.0.0 > cd kubernetes/examples/minikube
minikube > kubectl apply -f .
{code}
 

 # Check pod statuses

{code:java}
minikube > kubectl get pod
NAME         READY   STATUS             RESTARTS        AGE
datanode-0   1/1     Running            0               10m
datanode-1   1/1     Running            0               10m
datanode-2   1/1     Running            0               10m
httpfs-0     0/1     CrashLoopBackOff   6 (2m25s ago)   10m
om-0         1/1     Running            0               10m
recon-0      1/1     Running            0               10m
s3g-0        0/1     CrashLoopBackOff   6 (2m25s ago)   10m
scm-0        1/1     Running            0               10m {code}

 # Check events

{code:java}
minikube > kubectl events

...

10m (x6 over 14m)       Normal    Created    Pod/s3g-0           Created container: s3g
10m (x6 over 14m)       Normal    Started    Pod/s3g-0           Started container s3g
10m (x6 over 14m)       Normal    Started    Pod/httpfs-0        Started container httpfs
10m (x6 over 14m)       Normal    Created    Pod/httpfs-0        Created container: httpfs
9m28s (x6 over 13m)     Normal    Killing    Pod/s3g-0           Container s3g failed liveness probe, will be restarted
9m18s (x6 over 13m)     Normal    Killing    Pod/httpfs-0        Container httpfs failed liveness probe, will be restarted
8m10s (x8 over 9m28s)   Warning   BackOff    Pod/s3g-0           Back-off restarting failed container s3g in pod s3g-0_default(b047ddba-062e-4d02-b3e9-622222a5d1ba)
8m8s (x8 over 9m18s)    Warning   BackOff    Pod/httpfs-0        Back-off restarting failed container httpfs in pod httpfs-0_default(1c2db5b1-5d02-46e7-90fd-841658a18c8d)
4m16s (x7 over 13m)     Normal    Pulled     Pod/s3g-0           Container image "apache/ozone:2.0.0" already present on machine
4m11s (x7 over 13m)     Normal    Pulled     Pod/httpfs-0        Container image "apache/ozone:2.0.0" already present on machine
3m38s (x22 over 13m)    Warning   Unhealthy  Pod/s3g-0           Liveness probe failed: HTTP probe failed with statuscode: 403
3m37s (x18 over 13m)    Warning   Unhealthy  Pod/httpfs-0        Liveness probe failed: HTTP probe failed with statuscode: 500
{code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org