Resource Orchestration Service (ROS) generates status for operations on stack groups and stack instances.

Stack group operations

Status of a stack group operation Description
RUNNING The operation is in progress.
SUCCEEDED The operation is succeeded and the fault tolerance capability is not exceeded.
FAILED The number of stacks on which the operation failed exceeds the fault tolerance capability.
STOPPING The operation is being stopped.
STOPPED The operation is stopped.
QUEUED The operation is queued. If an operation is being performed on a stack group that has service-managed permissions when ROS attempts to deploy a stack instance, the automatic deployment for the stack instance is queued. For more information, see Enable automatic deployment for stack instances.

Stack instance operations

Status of a stack instance operation Description
CURRENT The stack is up to date with the stack group. The template and parameters of the stack are the same as those of the stack group.
OUTDATED The stack is not up to date with the stack group. The template and parameters of the stack are different from those of the stack group. Stack instances may enter the state due to the following reasons:
  • The stack group and specific stack instances are updated. In this case, the stack instances that are not updated enter the OUTDATED state.
  • When ROS creates or updates stack instances, ROS fails to assume the required role. The stacks that correspond to the stack instances cannot be created or updated. In this case, the stack instances enter the OUTDATED state.
  • When ROS creates or updates stack instances, ROS assumes the required role. However, the stacks that correspond to the stack instances cannot be created or updated. In this case, the stack instances enter the OUTDATED state.