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

Controller fails to start when opentrace is enabled #4924

Closed
yafernandes opened this issue Jan 14, 2020 · 1 comment
Closed

Controller fails to start when opentrace is enabled #4924

yafernandes opened this issue Jan 14, 2020 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@yafernandes
Copy link

yafernandes commented Jan 14, 2020

NGINX Ingress controller version: 0.27.0

Kubernetes version: 1.16.4

Environment:

  • Cloud provider or hardware configuration: AWS
  • OS (e.g. from /etc/os-release): Ubuntu 19.10
  • Kernel (e.g. uname -a): 5.3.0-1007-aws
  • Install tools: Helm 3, Chart stable/nginx-ingress 1.29.1
  • Others:

What happened:

nginx: [error] Failed to load tracing library /usr/local/lib/libdd_opentracing.so: Error loading shared library /usr/local/lib/libdd_opentracing.so: No such file or directory
nginx: configuration file /tmp/nginx-cfg869960893 test failed

-------------------------------------------------------------------------------
W0114 13:26:54.648206       6 queue.go:130] requeuing initial-sync, err
-------------------------------------------------------------------------------
Error: exit status 1

ConfigMap

kind: ConfigMap
apiVersion: v1
metadata:
  name: nginx-nginx-ingress-controller
  labels:
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
data:
  # enable-opentracing: "true"
  datadog-collector-host: $HOST_IP

Helm values.yaml

controller:
  service:
    type: NodePort
    nodePorts:
      http: 30080
      https: 30443
  metrics:
    enabled: true
  extraEnvs:
    - name: HOST_IP
      valueFrom:
        fieldRef:
          fieldPath: status.hostIP

/kind bug

@yafernandes yafernandes added the kind/bug Categorizes issue or PR as related to a bug. label Jan 14, 2020
@aledbf
Copy link
Member

aledbf commented Jan 14, 2020

Closing. This is already fixed in master #4920
Today we plan to release 0.27.1 with the fix.

@aledbf aledbf closed this as completed Jan 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants