Our own Jenkins Pipeline projects seem to be getting stuck in this state of "master is offline" when attempting to run on our clusters which have zero executors assigned to the master node.
It's unclear what, past a service restart, will clear this up
Steps to reproduce:
- Start a pipeline job
- forcing the master to run out of storage
- shutdown master, clear up storage
- restart master, confirm it's up
- observe that it is still marked as offline for a long time. 30+ minutes