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

create san cert with panic #744

Closed
gavinzhou opened this issue Dec 5, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@gavinzhou
Copy link

commented Dec 5, 2017

voyager 5.0.0.rc6 is worked in my gke
I will create san cert tls , get panic error

more g-certificate.yaml
apiVersion: voyager.appscode.com/v1beta1
kind: Certificate
metadata:
  name: g-orangesys-cert
  namespace: apigateway
spec:
  domains:
  - demo.g.orangesys.io
  - fmsyon.g.orangesys.io
  acmeUserSecretName: stg-orangesys-user-secret
  challengeProvider:
    dns:
      provider: googlecloud
      credentialSecretName: saas-orangesys-io-gcp-secret
  storage:
    secret: {}
E1205 14:17:05.428930       1 runtime.go:66] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)
/go/src/github.com/appscode/voyager/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:72
/go/src/github.com/appscode/voyager/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:65
/go/src/github.com/appscode/voyager/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:51
/usr/local/go/src/runtime/asm_amd64.s:509
/usr/local/go/src/runtime/panic.go:491
/usr/local/go/src/runtime/panic.go:63
/usr/local/go/src/runtime/signal_unix.go:367
/go/src/github.com/appscode/voyager/pkg/certificate/controller.go:251
/go/src/github.com/appscode/voyager/pkg/certificate/controller.go:151
/go/src/github.com/appscode/voyager/pkg/operator/certificate_crds.go:59
/go/src/github.com/appscode/voyager/vendor/k8s.io/client-go/tools/cache/controller.go:195
<autogenerated>:1
/go/src/github.com/appscode/voyager/vendor/k8s.io/client-go/tools/cache/controller.go:314
/go/src/github.com/appscode/voyager/vendor/k8s.io/client-go/tools/cache/delta_fifo.go:451
/go/src/github.com/appscode/voyager/vendor/k8s.io/client-go/tools/cache/controller.go:150
/go/src/github.com/appscode/voyager/vendor/k8s.io/client-go/tools/cache/controller.go:124
/go/src/github.com/appscode/voyager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:133
/go/src/github.com/appscode/voyager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:134
/go/src/github.com/appscode/voyager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:88
/go/src/github.com/appscode/voyager/vendor/k8s.io/client-go/tools/cache/controller.go:124
/usr/local/go/src/runtime/asm_amd64.s:2337
@gavinzhou

This comment has been minimized.

Copy link
Author

commented Dec 5, 2017

kubectl exec -it voyager-operator-2315020022-3840g -n kube-system voyager version
Version = 5.0.0-rc.6
VersionStrategy = tag
Os = alpine
Arch = amd64
CommitHash = b6e41e6a30d3b31fa150abcb3dc57703ca9df5a7
GitBranch = release-5.0
GitTag = 5.0.0-rc.6
CommitTimestamp = 2017-12-05T01:41:34
@tamalsaha

This comment has been minimized.

Copy link
Member

commented Dec 5, 2017

Can you update your operator image to appscode/voyager:crt-panic ? I think this should fix the panic.

tamalsaha added a commit that referenced this issue Dec 5, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.