Differences

This shows you the differences between two versions of the page.

--- devel:documentation:roles:adm:role_assignment [2019/07/23 11:16]
svandav [Failed state]
+++ devel:documentation:roles:adm:role_assignment [2019/07/23 11:37]
svandav [Running state]
@@ Line 104: / Line 104: @@
 {{ :devel:documentation:roles:adm:request-inprogress.png?800 |}}
+**Second** situation when could be request in running state is if role assign **the virtula system**.
+If the request assign or changes an account on the virtual system, then the virtual system creates a request by default, pending implementation by the appropriate implementer. Our request to change roles will be in a running state until all possible requests on virtual systems are resolved. The purpose of this wait is to ensure that the final notification of the completion of the request is sent after the real implementation of the requirements on the systems representing the virtual systems.
+In this situation has system state **RUNNING** orange color and show message: **Some requests on this vritual systems [Name of vritual systems] are not resloved!**.
+{{ :devel:documentation:roles:adm:request-inprogress-on-vs.png?800 |}}
 ==== Failed state ====
@@ Line 135: / Line 143: @@
 {{ :devel:documentation:roles:adm:request-blocked.png?800 |}}
+==== Not executed state ====
+This state is **very similar to the case when the provisioning operation is blocked**. Occures where system is seta to **read only** mode.
 ===== Link to request from a provisioning operations =====