Examples of system state transitions
Prev	Cluster and system states	Next

---

Examples of system state transitions

• If VCS is started on a system, and if that system is the only one in the cluster with a valid configuration, the system transitions to the running state:

  initing -> current_discover_wait -> local_build -> running

• If VCS is started on a system with a valid configuration file, and if at least one other system is already in the RUNNING state, the new system transitions to the running state:

  initing -> current_discover_wait -> remote_build -> running

• If VCS is started on a system with an invalid configuration file, and if at least one other system is already in the RUNNING state, the new system transitions to the running state:

  initing -> stale_discover_wait -> remote_build -> running

• If VCS is started on a system with an invalid configuration file, and if all other systems are in stale_admin_wait state, the system transitions to the stale_admin_wait state as shown below. A system stays in this state until another system with a valid configuration file is started.

  initing -> stale_discover_wait -> stale_admin_wait

• If VCS is started on a system with a valid configuration file, and if other systems are in the ADMIN_WAIT state, the new system transitions to the admin_wait state.

  initing -> current_discover_wait -> admin_wait

• If VCS is started on a system with an invalid configuration file, and if other systems are in the admin_wait state, the new system transitions to the admin_wait state.

  initing -> stale_discover_wait -> admin_wait

• When a system in running state is stopped with the hastop command, it transitions to the exited state as shown below. During the leaving state, any online system resources are taken offline. When all of the system's resources are taken offline and the agents are stopped, the system transitions to the exiting state, then exited.

  running -> leaving -> exiting -> exited