-
Bug
-
Resolution: Fixed
-
Low
-
None
-
1
-
Severity 3 - Minor
-
68
-
Issue Summary
when we disable runners (tested with docker-linux version 1.559), one may notice the following exception in runners log, which will crash the runner
Exception in thread "Thread-0" java.lang.NullPointerException
Steps to Reproduce
-
- Setup a Runner (in UI and run the container)
- Disable the Runner in UI
- Runner status becomes OFFLINE in UI
Expected Results
The runner should be set to offline status, and enabling runners back should switch it to online status
Actual Results
Observe the following error in Runner log
[2024-03-01 09:58:11,994] Runner version: 1.559 [2024-03-01 09:58:12,010] Runner runtime: linux-docker [2024-03-01 09:58:12,063] Copying Docker cli to working directory. [2024-03-01 09:58:12,192] Starting websocket listening to RUNNER_UPDATED events. [2024-03-01 09:58:12,252] Updating runner status to "ONLINE" and checking for new steps assigned to the runner after 0 seconds and then every 30 seconds. [2024-03-01 09:58:12,343] Updating runner state to "ONLINE". [2024-03-01 09:58:42,259] Updating runner state to "ONLINE". [2024-03-01 09:59:12,265] Updating runner state to "ONLINE". Exception in thread "Thread-0" java.lang.NullPointerException at com.atlassian.pipelines.common.trace.rxjava.util.BraveUtil.lambda$withOptionalSpanInScope$0(BraveUtil.java:19) at java.base/java.util.Optional.map(Unknown Source) at com.atlassian.pipelines.common.trace.rxjava.util.BraveUtil.withOptionalSpanInScope(BraveUtil.java:19) at com.atlassian.pipelines.runner.core.util.RunnableWithContext.run(RunnableWithContext.java:31) at java.base/java.lang.Thread.run(Unknown Source)
Workaround
Currently, there is no workaround for this bug. Restarting the container and re-enabling the runners may help. If any workaround becomes available, it will be updated here