CloudBees Replication Parent 1927

In a High Availability (HA) controller, changes made to the permanent agents using the multi-executor option (additions, deletions, reconfigurations) while the controller is running are reflected in the list of read-only clones. However, applying jenkins.yaml from a CasC bundle that includes the jenkins.nodes section could change the list of agents without triggering the correct notifications, resulting in some cases in orphaned clones that could not be readily deleted. Now, a controller replica will explicitly check for orphaned clones during startup and remove them.

If a replica of a High Availability (HA) controller restarts in less than one minute and retains the same host name (for example, in Kubernetes if using the /exit REST endpoint instead of performing a rolling restart), a scheduled Pipeline build stage (that was waiting for an executor at the time) could be reread by the restarted replica before the adoptive owner of the build noticed. This prevents the stage from being run and ultimately causing the build to abort. Now, replicas will explicitly check for scheduled stages at startup that are intended to be managed by another replica and transfer them, allowing the build to complete.