-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.18.z
-
Quality / Stability / Reliability
-
False
-
-
None
-
Critical
-
None
-
Unspecified
-
Production
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
When attempting to deploy a new hosted cluster, the assisted-service container is entering a CrashLoopBackOff state. The container logs indicate that the applicaiton is terminating with signal SIGSEGV. While similar to OCPBUGS-25773, the backtrace at the time of the error is for different routines
Version-Release number of selected component (if applicable):
All versions to be confirmed OCP: 4.18.17 MCE: ?.?.? ACM: 2.9.?
How reproducible:
To be confirmed
Steps to Reproduce:
To be confirmed
Actual results:
The assisted-service container terminates with state CrashLoopBackOff and the new cluster is not created
Expected results:
The assisted-service container runs, nodes are discovered and the new cluster is created
Additional info:
The tail of the logs from the the assisted-serivice container after it crashes:
$ tail -22 assisted-service-xxxxxxxxxxx-xxxxx-assisted-service.log panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x68 pc=0x39243b4]goroutine 142 [running]: github.com/openshift/assisted-service/internal/common.GetDeviceIdentifier(...) /remote-source/assisted-service/app/internal/common/disks_info.go:87 github.com/openshift/assisted-service/internal/host.(*transitionHandler).replaceMacros(0xc000fa2780, {0x4cdd2a1?, 0x18611fd?}, 0xc001544588, 0xc001156580) /remote-source/assisted-service/app/internal/host/transition.go:726 +0x1b4 github.com/openshift/assisted-service/internal/host.(*transitionHandler).PostRefreshHost.func1({0x529a740?, 0xc001544588}, {0x42cadc0?, 0xc001156580}) /remote-source/assisted-service/app/internal/host/transition.go:755 +0x8c github.com/filanov/stateswitch.(*stateMachine).Run(0x4601be0?, {0x4b49b36?, 0x4601be0?}, {0x529a740, 0xc001544588}, {0x42cadc0, 0xc001156580}) /remote-source/assisted-service/app/vendor/github.com/filanov/stateswitch/statemachine.go:61 +0x1ca github.com/openshift/assisted-service/internal/host.(*Manager).refreshStatusInternal(0xc000ec43c0, {0x52beb00, 0xc000f727b0}, 0xc001115c08, 0xc0005d0108, 0x0, 0xc001473ec0, 0xc000536bd0) /remote-source/assisted-service/app/internal/host/host.go:495 +0x4ad github.com/openshift/assisted-service/internal/host.(*Manager).clusterHostMonitoring(0xc000ec43c0) /remote-source/assisted-service/app/internal/host/monitor.go:183 +0x4be github.com/openshift/assisted-service/internal/host.(*Manager).HostMonitoring(0xc000ec43c0) /remote-source/assisted-service/app/internal/host/monitor.go:266 +0x8f github.com/openshift/assisted-service/pkg/thread.(*Thread).loop(0xc000baa6e0) /remote-source/assisted-service/app/pkg/thread/thread.go:73 +0xa2 created by github.com/openshift/assisted-service/pkg/thread.(*Thread).Start in goroutine 1 /remote-source/assisted-service/app/pkg/thread/thread.go:43 +0xff
- relates to
-
OCPBUGS-25773 Assisted service pod remains in CrashLoopBackOff state after cluster creation
-
- Closed
-