Manual Intervention step fails

(Tudor Iftimie) #1

hi,
I created a small project to simulate the problem we have with the approval of production deployments.

Problem: When the workflow reaches the approval step it fails after the the user clicks “Proceed”.
After a random number of retries it works without performing any changes.

Here is how I reproduced the error:
step 1 : approval
step2: run powershell script

the approval is configured like this:

when I run it, this is how it looks:

(Daniel Fischer) #3

Hi @tudor.iftimie,

Thanks for getting in touch! I’m sorry for the delay in getting back to you here.

Would you be able to let me know what version of Octopus deploy you are currently running?

Would you be able to attach the raw deployment log for a deployment where this is failing, and one where it succeeds?

The following docs page has instructions on downloading the raw deployment logs.

Looking forward to hearing from you and getting to the bottom of this. :slight_smile:

Best regards,
Daniel

(Tudor Iftimie) #4

Hi Daniel,

Thank you for the reply.
Please bear in mind that after a random number of retries it works.
Octopus version : 4.1.9 (licensed, in premises installation)

Raw log:
Task ID: ServerTasks-36227
Task status: Failed
Task queued: 27 February 2019 08:07
Task started: 27 February 2019 08:07
Task duration: 8 seconds
Server version: 4.1.9+Branch.master.Sha.40608f0cc50ccd1a6f9e3d404e8e0139924a07d4
Server node: TFS3

                | == Failed: Deploy AutoBuildRelease-TESTS release 1.3.1.6-try-12 to DEV ==

08:07:10 Verbose | Guided failure is not enabled for this task
|
| == Success: Step 1: approve ==
08:07:11 Verbose | approve completed
|
| Success: Octopus Server
08:07:10 Verbose | Octopus Server version: 4.1.9+Branch.master.Sha.40608f0cc50ccd1a6f9e3d404e8e0139924a07d4
08:07:10 Verbose | Environment Information:
| OperatingSystem: Microsoft Windows NT 6.3.9600.0
| OsBitVersion: x64
| Is64BitProcess: True
| CurrentUser: cosanostra\Octopus
| MachineName: TFS3
| ProcessorCount: 2
| CurrentDirectory: C:\Windows\system32
| TempDirectory: C:\Users\octopus\AppData\Local\Temp
| HostProcessName: Octopus.Server
| PID: 3880
08:07:10 Info | Pausing the deployment while manual intervention is requested
08:07:10 Verbose | Successfully finished approve on the Octopus Server
|
| == Pending: Step 2: Pull Scripts repository and execute deployment command 1 ==
|

(Tudor Iftimie) #5

Hi Daniel,

I have replied in the thread as external e-mail in Broadridge is delayed and attachments are not possible.

It looks like next step fails to capture the success of the approval step. After 5-10 seconds it will display “failed” status.

Clicking “retry” and re-approving solves the problem but the number of failures seems random to me.

We have on premises Octopus 4.1.9 licensed.

Raw log:

Task ID: ServerTasks-36227

Task status: Failed

Task queued: 27 February 2019 08:07

Task started: 27 February 2019 08:07

Task duration: 8 seconds

Server version: 4.1.9+Branch.master.Sha.40608f0cc50ccd1a6f9e3d404e8e0139924a07d4

Server node: xxxxx

== Failed: Deploy AutoBuildRelease-TESTS release 1.3.1.6-try-12 to DEV ==

08:07:10 Verbose | Guided failure is not enabled for this task

== Success: Step 1: approve ==

08:07:11 Verbose | approve completed

Success: Octopus Server

08:07:10 Verbose | Octopus Server version: 4.1.9+Branch.master.Sha.40608f0cc50ccd1a6f9e3d404e8e0139924a07d4

08:07:10 Verbose | Environment Information:

  OperatingSystem: Microsoft Windows NT 6.3.9600.0
  OsBitVersion: x64
  Is64BitProcess: True
  CurrentUser: xxxxxx\Octopus
  MachineName: TFS3
  ProcessorCount: 2
  CurrentDirectory: C:\Windows\system32
  TempDirectory: C:\Users\octopus\AppData\Local\Temp\
  HostProcessName: Octopus.Server
  PID: 3880

08:07:10 Info | Pausing the deployment while manual intervention is requested

08:07:10 Verbose | Successfully finished approve on the Octopus Server

(system) closed #6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.