In https://github.com/ansible/eda-server/pull/916 I introduced a bug making the creation of the activation instance an atomic operation, we call inside the operation the "set_status" as part of the check for new processes and raise an exception, so when the check is true, the transaction is undone and the activation remains in "starting" status.
In https://github.com/ansible/eda-server/pull/916 I introduced a bug making the creation of the activation instance an atomic operation, we call inside the operation the "set_status" as part of the check for new processes and raise an exception, so when the check is true, the transaction is undone and the activation remains in "starting" status.
Jira: https://issues.redhat.com/browse/AAP-25010