# Unable to launch Kubernetes cluster in s390x arch Travis instance

**URL:** <https://travis-ci.community/t/unable-to-launch-kubernetes-cluster-in-s390x-arch-travis-instance/12628>\
**Category:** Multi CPU Architecture\
**Created:** [January 25, 2022, 1:37pm UTC](https://travis-ci.community/t/unable-to-launch-kubernetes-cluster-in-s390x-arch-travis-instance/12628 "2022-01-25T13:37:55Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rposts](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/rposts/32/7635_2.png) [@rposts](https://travis-ci.community/u/rposts)\
**Post date:** [January 25, 2022, 1:37pm UTC](https://travis-ci.community/t/unable-to-launch-kubernetes-cluster-in-s390x-arch-travis-instance/12628/1 "2022-01-25T13:37:55Z")

</div>

Hi there,

Creating a Kubernetes cluster in s390x Travis instance fails to start up with following messages:

```auto
....
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
I0124 18:10:14.588971 8024 local.go:65] [etcd] wrote Static Pod manifest for a local etcd member to "/etc/kubernetes/manifests/etcd.yaml"
I0124 18:10:14.588983 8024 waitcontrolplane.go:91] [wait-control-plane] Waiting for the API server to be healthy
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.

```

I am able to successfully trigger kube builds on amd64.

Please let me know what could be going on here. Thanks.

Failed build:

> **[Travis CI - Test and Deploy with Confidence](https://app.travis-ci.com/github/linux-on-ibm-z/strimzi-kafka-operator/jobs/556788599)**
>
> Travis CI enables your team to test and ship your apps with confidence. Easily sync your projects with Travis CI and you'll be testing your code in minutes.

---

<div class="post-metadata">

**Author:** ![Montana](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/montana/32/9566_2.png) [@Montana](https://travis-ci.community/u/Montana)\
**Post date:** [February 1, 2022, 3:13pm UTC](https://travis-ci.community/t/unable-to-launch-kubernetes-cluster-in-s390x-arch-travis-instance/12628/2 "2022-02-01T15:13:20Z")

</div>

Try adding this in your `script` hook:

```bash
sudo swapoff -a
sudo sed -i '/ swap / s/^/#/' /etc/fstab

```

---

<div class="post-metadata">

**Author:** ![rposts](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/rposts/32/7635_2.png) [@rposts](https://travis-ci.community/u/rposts)\
**Post date:** [February 3, 2022, 3:02pm UTC](https://travis-ci.community/t/unable-to-launch-kubernetes-cluster-in-s390x-arch-travis-instance/12628/3 "2022-02-03T15:02:19Z")

</div>

Hi @Montana - thanks for your input. I had already tried the `swapoff` tweak earlier but it did not help. I also added `fstab` step to my script but it did not work either.

> **[Travis CI - Test and Deploy with Confidence](https://app.travis-ci.com/github/linux-on-ibm-z/strimzi-kafka-operator/builds/245867199)**
>
> Travis CI enables your team to test and ship your apps with confidence. Easily sync your projects with Travis CI and you'll be testing your code in minutes.

---

<div class="post-metadata">

**Author:** ![Montana](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/montana/32/9566_2.png) [@Montana](https://travis-ci.community/u/Montana)\
**Post date:** [February 3, 2022, 7:34pm UTC](https://travis-ci.community/t/unable-to-launch-kubernetes-cluster-in-s390x-arch-travis-instance/12628/4 "2022-02-03T19:34:09Z")

</div>

Hey @rposts,

Let me look into this a bit further. Thanks for the link. I’ll post back when I have more information.

---

<div class="post-metadata">

**Author:** ![velemas](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/velemas/32/7395_2.png) [@velemas](https://travis-ci.community/u/velemas)\
**Post date:** [March 10, 2022, 8:39am UTC](https://travis-ci.community/t/unable-to-launch-kubernetes-cluster-in-s390x-arch-travis-instance/12628/5 "2022-03-10T08:39:39Z")

</div>

Hi @Montana any news on this? This blocks us too. The problem seems to be in LXD container which is not suitable for Kubernetes. We need a full VM. Looks like linux-ppc64le provides this for Power [The Travis CI Blog: Build your open source projects on IBM Power and IBM Z CPU architecture](https://blog.travis-ci.com/2019-11-12-multi-cpu-architecture-ibm-power-ibm-z) but there is no linux-s390x for Z.