Well those logs aren’t great on their own!
Even cloning this particular working step to another project causes it once again to fail in the other project.
This is also very odd.
As there may be some sensitive details in the next logs that I’m going to request from you, I’ll request you use the following link to upload your files.
However, please let us know by responding to this ticket, when you have uploaded some files.
Back to the issue:
Have you recently done an Octopus Server upgrade around the same time that you saw these issues?
I’m looking through the logs and although they aren’t super clear, I did notice the following:
11:57:23 Info | Use Published Snapshot Before Check: True
11:57:23 Info | Runbook Name Newman Tests - Grouptool
11:57:23 Info | Runbook Base Url: https://octopus.wur.nl
11:57:23 Info | Runbook Space Name:
11:57:23 Info | Runbook Environment Name: Server Environment
11:57:23 Info | Runbook Tenant Name:
11:57:23 Info | Wait for Finish: False
11:57:23 Info | Use Guided Failure: False
11:57:23 Info | Cancel run in seconds: 0
11:57:23 Info | Use Published Snapshot: True
If this is accurate, is seems like the “Space Name” is blank. Version 2022.1.2495 definitely requires the Spaces argument.
I’m assuming this is coming from the Runbooks variables.
Can you make sure your “Run Octopus Deploy Runbook” configuration includes the SpaceName variable.
Are you also able to publish a new runbook snapshot? The variables will likely not have changed, but it might be retaining information about the snapshot before Spaces were included.
I think this should be the first thing that you try. If this doesn’t get you closer to a solution, would you be able to return the results of the following API calls?
You will need to update the Projects-X with the Project-ID of the Project with your runbook
Additionally, a HAR file might provide us with some additional information that could come in handy as well.
We should be able to get a decent idea of what is missing from those results.