If CloudBees High Availability (HA) is not working as expected, use this page to troubleshoot.
High Availability (HA) developer mode
The High Availability (HA) feature provides a developer mode to troubleshoot HA problems in controllers running in HA mode.
To enable the developer mode in a controller.
-
Navigate to
. -
Select the Enable developer mode field and select Save or Apply.
![Figure 1. Enable developer mode Enable developer mode](_images/ha-developer-mode.3f24a4a.png)
Developer mode is a powerful tool to troubleshoot and understand High Availability. When enabled, the controller provides additional information about the High Availability mode:
-
The replica name appears in the page footer.
-
The background color for the footer changes from one replica to another.
Figure 2. Footer in developer mode. -
The consolidated queue widget notes the queue items in other replicas.
-
The name of running builds adds the name of the replica that owns the build.
![Figure 3. Build name in developer mode Build name in developer mode](_images/ha-build-name.84f0273.png)
In addition to the developer mode, also from the High Availability screen, users can change the replica they are using by selecting the Reset sticky session button.
![Figure 4. Switch to another replica Switch to another replica](_images/ha-reset-sticky-session.8a58105.png)
When the Reset sticky session is selected, CloudBees CI randomly assigns a new replica to the user. If there is no change and they are assigned to the same replica, users can reload the page and try again until a new replica is assigned |
Problems with a CloudBees CI on modern cloud platforms installations
Controller configuration is not set to Deployment
If the controller fails to provision with the error:
ERROR: Failed to provision controller ... StatefulSet is only for non-replicated controllers
The issue was caused by including kind: StatefulSet
when configuring the controller under Advanced configuration
→ YAML
.
To resolve the issue, click Acknowledge error
, Free snapshot
, then go to the configuration page and change kind: StatefulSet
to kind: Deployment
in the YAML
field.