Build fails with segmentation violation error

Solution Unverified - Updated -

Issue

  • Build started failing on cluster with a traceback
  • The traceback when build fails:
fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0x6162 pc=0x7f2c48ac62a0]

runtime stack:
runtime.throw(0x3f4de93, 0x2a)
        /usr/lib/golang/src/runtime/panic.go:566 +0x95
runtime.sigpanic()
        /usr/lib/golang/src/runtime/sigpanic_unix.go:12 +0x2cc

goroutine 1 [running, locked to thread]:
runtime.asmcgocall(0x7f2c48af6130, 0xc420028748)
        /usr/lib/golang/src/runtime/asm_amd64.s:575 +0x42 fp=0xc420028730 sp=0xc420028728

goroutine 17 [syscall, locked to thread]:
runtime.goexit()
        /usr/lib/golang/src/runtime/asm_amd64.s:2086 +0x1

Environment

  • OpenShift Container Platform 3.6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In