You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
service/postgres-for-dev created
replicationcontroller/postgres created
error: unrecognized condition: "jsonpath=***.status.loadBalancer.ingress[0].ip***"
Error: Process completed with exit code 1.
Issue Failure
Failure: Test is continually failing
Issue Priority
Priority: 2 (backlog / disabled test but we think the product is healthy)
Issue Components
Component: Python SDK
Component: Java SDK
Component: Go SDK
Component: Typescript SDK
Component: IO connector
Component: Beam YAML
Component: Beam examples
Component: Beam playground
Component: Beam katas
Component: Website
Component: Spark Runner
Component: Flink Runner
Component: Samza Runner
Component: Twister2 Runner
Component: Hazelcast Jet Runner
Component: Google Cloud Dataflow Runner
The text was updated successfully, but these errors were encountered:
Run kubectl apply -f /runner/_work/beam/beam/.test-infra/kubernetes/hadoop/LargeITCluster/hdfs-multi-datanode-cluster.yml
service/hadoop created
service/hadoop-datanodes created
statefulset.apps/datanode created
pod/namenode-0 created
error: unrecognized condition: "jsonpath=***.status.loadBalancer.ingress[0].ip***"
Error: Process completed with exit code 1.
Run kubectl apply -f /runner/_work/beam/beam/.test-infra/kubernetes/hadoop/LargeITCluster/hdfs-multi-datanode-cluster.yml
service/hadoop created
service/hadoop-datanodes created
statefulset.apps/datanode created
pod/namenode-0 created
error: unrecognized condition: "jsonpath=***.status.loadBalancer.ingress[0].ip***"
Error: Process completed with exit code 1.
What happened?
Example run: https://github.com/apache/beam/actions/runs/6380840947/job/17318812300
Log:
Issue Failure
Failure: Test is continually failing
Issue Priority
Priority: 2 (backlog / disabled test but we think the product is healthy)
Issue Components
The text was updated successfully, but these errors were encountered: