ingress-nginx: ingress-nginx-controller pod fails to start on s390x
NGINX Ingress controller version: v0.41.2
Kubernetes version (use kubectl version
):
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", BuildDate:"2020-10-14T12:50:19Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/s390x"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"d360454c9bcd1634cf4cc52d1867af5491dc9c5f", GitTreeState:"clean", BuildDate:"2020-11-11T13:09:17Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/s390x"}
Environment:
- OS (e.g. from /etc/os-release): Ubuntu:20.10
- Kernel (e.g.
uname -a
):Linux host 5.8.0-26-generic #27-Ubuntu SMP Wed Oct 21 22:24:40 UTC 2020 s390x s390x s390x GNU/Linux
What happened:
Below error messages were observed in the pods logs:
root@host:/home/ubuntu# docker logs 6dd74d3f2a22
-------------------------------------------------------------------------------
NGINX Ingress controller
Release: v0.41.2
Build: d8a93551e6e5798fc4af3eb910cef62ecddc8938
Repository: https://github.com/kubernetes/ingress-nginx
nginx version: nginx/1.19.4
-------------------------------------------------------------------------------
I1123 09:49:31.976294 6 flags.go:205] "Watching for Ingress" class="nginx"
W1123 09:49:31.976358 6 flags.go:210] Ingresses with an empty class will also be processed by this Ingress controller
W1123 09:49:31.976573 6 client_config.go:608] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
I1123 09:49:31.976732 6 main.go:241] "Creating API client" host="https://10.96.0.1:443"
I1123 09:49:31.983909 6 main.go:285] "Running in Kubernetes cluster" major="1" minor="19" git="v1.19.4" state="clean" commit="d360454c9bcd1634cf4cc52d1867af5491dc9c5f" platform="linux/s390x"
I1123 09:49:32.260115 6 main.go:105] "SSL fake certificate created" file="/etc/ingress-controller/ssl/default-fake-certificate.pem"
I1123 09:49:32.260983 6 main.go:115] "Enabling new Ingress features available since Kubernetes v1.18"
W1123 09:49:32.262482 6 main.go:127] No IngressClass resource with name nginx found. Only annotation will be used.
I1123 09:49:32.271800 6 ssl.go:528] "loading tls certificate" path="/usr/local/certificates/cert" key="/usr/local/certificates/key"
I1123 09:49:32.300660 6 nginx.go:249] "Starting NGINX Ingress controller"
I1123 09:49:32.304931 6 event.go:282] Event(v1.ObjectReference{Kind:"ConfigMap", Namespace:"ingress-nginx", Name:"ingress-nginx-controller", UID:"1a020af8-364f-4680-8420-da8f836890e8", APIVersion:"v1", ResourceVersion:"659", FieldPath:""}): type: 'Normal' reason: 'CREATE' ConfigMap ingress-nginx/ingress-nginx-controller
I1123 09:49:33.501193 6 nginx.go:291] "Starting NGINX process"
I1123 09:49:33.501265 6 leaderelection.go:243] attempting to acquire leader lease ingress-nginx/ingress-controller-leader-nginx...
I1123 09:49:33.501549 6 nginx.go:311] "Starting validation webhook" address=":8443" certPath="/usr/local/certificates/cert" keyPath="/usr/local/certificates/key"
I1123 09:49:33.501817 6 controller.go:144] "Configuration changes detected, backend reload required"
2020/11/23 09:49:33 [error] 31#31: failed to run the Lua code for coroutine_api: 4396981146480: coroutine_api:2: attempt to call global 'require' (a nil value)
nginx: [error] failed to run the Lua code for coroutine_api: 4396981146480: coroutine_api:2: attempt to call global 'require' (a nil value)
2020/11/23 09:49:33 [alert] 31#31: failed to load the 'resty.core' module (https://github.com/openresty/lua-resty-core); ensure you are using an OpenResty release from https://openresty.org/en/download.html (reason: /usr/local/lib/lua/resty/core.lua:3: attempt to index global 'ngx' (a nil value)) in /etc/nginx/nginx.conf:5
nginx: [alert] failed to load the 'resty.core' module (https://github.com/openresty/lua-resty-core); ensure you are using an OpenResty release from https://openresty.org/en/download.html (reason: /usr/local/lib/lua/resty/core.lua:3: attempt to index global 'ngx' (a nil value)) in /etc/nginx/nginx.conf:5
W1123 09:49:33.506095 6 nginx.go:34]
-------------------------------------------------------------------------------
NGINX master process died (1): exit status 1
-------------------------------------------------------------------------------
I1123 09:49:33.507477 6 leaderelection.go:253] successfully acquired lease ingress-nginx/ingress-controller-leader-nginx
I1123 09:49:33.507511 6 status.go:84] "New leader elected" identity="ingress-nginx-controller-5dbd9649d4-jlrn7"
I1123 09:49:33.514461 6 status.go:205] "POD is not ready" pod="ingress-nginx/ingress-nginx-controller-5dbd9649d4-jlrn7" node="host"
E1123 09:49:33.547937 6 controller.go:156] Unexpected failure reloading the backend:
exit status 1
2020/11/23 09:49:33 [notice] 39#39: signal process started
2020/11/23 09:49:33 [error] 39#39: invalid PID number "" in "/tmp/nginx.pid"
nginx: [error] invalid PID number "" in "/tmp/nginx.pid"
E1123 09:49:33.548014 6 queue.go:130] "requeuing" err="exit status 1\n2020/11/23 09:49:33 [notice] 39#39: signal process started\n2020/11/23 09:49:33 [error] 39#39: invalid PID number \"\" in \"/tmp/nginx.pid\"\nnginx: [error] invalid PID number \"\" in \"/tmp/nginx.pid\"\n" key="initial-sync"
I1123 09:49:33.548191 6 event.go:282] Event(v1.ObjectReference{Kind:"Pod", Namespace:"ingress-nginx", Name:"ingress-nginx-controller-5dbd9649d4-jlrn7", UID:"148c5a71-4812-4827-95ad-ec21784aad8a", APIVersion:"v1", ResourceVersion:"3062", FieldPath:""}): type: 'Warning' reason: 'RELOAD' Error reloading NGINX: exit status 1
2020/11/23 09:49:33 [notice] 39#39: signal process started
2020/11/23 09:49:33 [error] 39#39: invalid PID number "" in "/tmp/nginx.pid"
nginx: [error] invalid PID number "" in "/tmp/nginx.pid"
I1123 09:49:36.835301 6 controller.go:144] "Configuration changes detected, backend reload required"
E1123 09:49:36.879828 6 controller.go:156] Unexpected failure reloading the backend:
exit status 1
2020/11/23 09:49:36 [notice] 47#47: signal process started
2020/11/23 09:49:36 [error] 47#47: invalid PID number "" in "/tmp/nginx.pid"
What you expected to happen:
ingress-nginx-controller pod should be up and running
How to reproduce it:
kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/provider/baremetal/deploy.yaml
Anything else we need to know:
/kind bug
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 1
- Comments: 20 (11 by maintainers)
Commits related to this issue
- This PR fixes issue https://github.com/openresty/luajit2/issues/136 and breakage introduced by commit 5980ef945c459625a21d8f397fb8a4cf043c1771 seen in https://github.com/kubernetes/ingress-nginx/issue... — committed to velemas/luajit2 by velemas 3 years ago
- This PR fixes issue https://github.com/openresty/luajit2/issues/136 and breakage introduced by commit 5980ef945c459625a21d8f397fb8a4cf043c1771 seen in https://github.com/kubernetes/ingress-nginx/issue... — committed to velemas/luajit2 by velemas 3 years ago
- This PR fixes issue https://github.com/openresty/luajit2/issues/136 and breakage introduced by commit 5980ef945c459625a21d8f397fb8a4cf043c1771 seen in https://github.com/kubernetes/ingress-nginx/issue... — committed to velemas/luajit2 by velemas 3 years ago
- bugfix: This PR fixes issue https://github.com/openresty/luajit2/issues/136 (#144) and breakage introduced by commit 5980ef945c459625a21d8f397fb8a4cf043c1771 seen in https://github.com/kubernetes/in... — committed to openresty/luajit2 by velemas 3 years ago
Awesome 😃 closing this one
/close
Tested the latest controller image with tag v1.0.0. This image has the changes in PR #7355 included. I checked the image and it seems to be working fine on s390x architecture.