Parent rolling step continues after manual intervention in child

[droyad]

Steps to reproduce:

1. Create a project (Child) that has
   • Manual Intervention
   • Script step that sleeps for 30 seconds
2. Create a project (Parent) that has a rolling step with
   • Deploy release
   • Run script that says 'Hello'
3. Create a release of Parent and deploy it
4. Resolve the child's manual intervention when it occurs
5. Note that the 'Hello' action runs shortly after the intervention is resolved

Parent process:

Parent log:

Child log:

Expected

The Hello action runs after the child deployment completes (at least 30 seconds later)

[mcasperson]

Unfortunately QRF did not have capacity to look at this issue. The QRF card was archived, but if the issue comes through support again we will attempt to place it in the backlog.

[KennethBates]

I've reproduced what looks like the same behavior outside of a rolling step in the parent. It looks like acting on the manual intervention in the child immediately marks the deploy a release step in the parent as a success, even if the child project deploying is still ongoing. Reported here (private): https://octopus.zendesk.com/agent/tickets/170184

[octoreleasebot]

Release Note: Fix: Parent deployments does not wait for child deployments to complete after an interruption

[Octobob]

:tada: The fix for this issue has been released in:

Release stream	Release
2024.2	2024.2.7164
2024.3+	all releases