Uploaded image for project: 'Knative Serving'
  1. Knative Serving
  2. SRVKS-677

autoscaler "panic: runtime error: invalid memory address or nil pointer dereference" during kpa.(*Reconciler).ReconcileKind

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • 1.12.0
    • 1.12.0
    • None
    • Serverless Sprint 194 & 195

      During a 12h soak test, the autoscaler container restarted 5 times, with the most recent restart being caused by SIGSEGV:

      panic: runtime error: invalid memory address or nil pointer dereference
      [signal SIGSEGV: segmentation violation code=0x1 addr=0x60 pc=0x1808bfd]
      
      goroutine 166 [running]:
      knative.dev/serving/pkg/reconciler/autoscaling/kpa.(*Reconciler).ReconcileKind(0xc00043f5c0, 0x20a1020, 0xc003d708a0, 0xc0044a6240, 0x2066f60, 0xc0044a63f8)
      	/opt/app-root/src/go/src/knative.dev/serving/pkg/reconciler/autoscaling/kpa/kpa.go:151 +0x14fd
      knative.dev/serving/pkg/client/injection/reconciler/autoscaling/v1alpha1/podautoscaler.(*reconcilerImpl).Reconcile(0xc0002dd340, 0x20a1020, 0xc003d70720, 0xc0044b0720, 0x26, 0xc003b87888, 0x20a1020)
      	/opt/app-root/src/go/src/knative.dev/serving/pkg/client/injection/reconciler/autoscaling/v1alpha1/podautoscaler/reconciler.go:255 +0x1447
      knative.dev/pkg/controller.(*Impl).processNextWorkItem(0xc000504240, 0xc00019cf00)
      	/opt/app-root/src/go/src/knative.dev/serving/vendor/knative.dev/pkg/controller/controller.go:513 +0x708
      knative.dev/pkg/controller.(*Impl).RunContext.func3(0xc002fcde30, 0xc000504240)
      	/opt/app-root/src/go/src/knative.dev/serving/vendor/knative.dev/pkg/controller/controller.go:451 +0x53
      created by knative.dev/pkg/controller.(*Impl).RunContext
      	/opt/app-root/src/go/src/knative.dev/serving/vendor/knative.dev/pkg/controller/controller.go:449 +0x19c
      

              rhn-support-knakayam Kenjiro Nakayama (Inactive)
              maschmid@redhat.com Marek Schmidt
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: