Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

quay.io/kubernetes-ingress-controller/nginx-ingress-controller-s390x:0.12.0 image not working on s390x #2295

Closed
srajmane opened this issue Apr 5, 2018 · 5 comments · Fixed by #2333

Comments

@srajmane
Copy link

srajmane commented Apr 5, 2018

Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/.):

What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.):


Is this a BUG REPORT or FEATURE REQUEST? (choose one):BUG

NGINX Ingress controller version: 0.12.0

Kubernetes version (use kubectl version): 1.9.6

Environment:

  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release): Ubuntu 16.04 and RHEL 7.3
  • Kernel (e.g. uname -a): s390x
  • Install tools: docker
  • Others:

What happened:
I am trying to deploy nginx-ingress-controller, but nginx-ingress-controller POD is not getting up.
default-http-backend POD is running.
Using gcr.io/google-containers/defaultbackend-s390x:1.4 image in default-backend.yaml
and for nginx-ingress-controller I am using quay.io/kubernetes-ingress-controller/nginx-ingress-controller-s390x:0.12.0 in with-rbac.yaml.
I also tried to build local docker image for nginx-ingress-controller and nginx, but still I am not able to start nginx-ingress-controller POD.

What you expected to happen:
Using this quay.io/kubernetes-ingress-controller/nginx-ingress-controller-s390x:0.12.0 image POD should get up on s390x.

Anything else we need to know:
Please check error log in comment section.

@srajmane
Copy link
Author

srajmane commented Apr 5, 2018

init_by_lua error: /usr/local/lib/lua/resty/core/uri.lua:4: module 'ffi' not found:
        no field package.preload['ffi']
        no file '/etc/nginx/lua/ffi.lua'
        no file '/etc/nginx/lua/vendor/ffi.lua'
        no file '/usr/local/lib/lua/ffi.lua'
        no file './ffi.lua'
        no file '/usr/local/share/lua/5.1/ffi.lua'
        no file '/usr/local/share/lua/5.1/ffi/init.lua'
        no file '/usr/local/lib/lua/5.1/ffi.lua'
        no file '/usr/local/lib/lua/5.1/ffi/init.lua'
        no file '/usr/share/lua/5.1/ffi.lua'
        no file '/usr/share/lua/5.1/ffi/init.lua'
        no file '/usr/local/lib/lua/ffi.so'
        no file '/usr/lib/x86_64-linux-gnu/lua/5.1/ffi.so'
        no file './ffi.so'
        no file '/usr/local/lib/lua/5.1/ffi.so'
        no file '/usr/lib/s390x-linux-gnu/lua/5.1/ffi.so'
        no file '/usr/lib/lua/5.1/ffi.so'
        no file '/usr/local/lib/lua/5.1/loadall.so'

@aledbf
Copy link
Member

aledbf commented Apr 5, 2018

Closing. Fixed in #2298
The error is related to the new dynamic configuration feature not available in s390x (LuJIT)

@aledbf aledbf closed this as completed Apr 5, 2018
@srajmane
Copy link
Author

srajmane commented Apr 9, 2018

I have changed flags.go file as per fix and built nginx-ingress-controller with make ARCH=s390x build container and created docker image. Edit with-rbac.yaml with new docker image, but still I am facing same issue "init_by_lua error: /usr/local/lib/lua/resty/core/uri.lua:4: module 'ffi' not found:"

@gyliu513
Copy link
Contributor

gyliu513 commented Apr 11, 2018

@aledbf even after apply your patch, we still have the same issue, can you help check? I think that we still need this open.

@oilbeater
Copy link
Contributor

only this patch cannot fix the problem, you should also update the nginx.tmpl in #2263.
However I see the master nginx.tmpl still leak some lua part if enable waf , this part should also be removed @aledbf

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants