We have implemented create release step using VSTS to deploy through octopus but when the build is triggered we are getting 400 Bad request error.
2018-09-24T18:00:04.2415923Z ##[section]Starting: Create Octopus Release: Smart_Service.ERollOff
2018-09-24T18:00:04.2423067Z Task : Create Octopus Release
2018-09-24T18:00:04.2423204Z Description : Create a Release in Octopus Deploy
2018-09-24T18:00:04.2423363Z Version : 2.0.135
2018-09-24T18:00:04.2423605Z Author : Octopus Deploy
2018-09-24T18:00:04.2423769Z Help : Version: 2.0.135. More Information
2018-09-24T18:00:08.0667668Z Environment = TfsVersionControl
2018-09-24T18:00:08.0668360Z Comments = True, WorkItems = True
2018-09-24T18:00:08.5956383Z ##[error]The remote server returned an error: (400) Bad Request.
2018-09-24T18:00:08.6090877Z ##[section]Finishing: Create Octopus Release:
I am also experiencing this same issue. Just started in the past hour after multiple successes throughout the day.
The following error is showing up inside octopus in the diagnostic logs:
The I/O operation has been aborted because of either a thread exit or an application request
It is successfully pushing packages to octopus but failing on the create release step
Hi @ramya_surendranath, thanks for reaching out.
Can you please try disabling the Comments and WorkItems and see if that allows the release to be created.
Also can you please attach the Octopus server logs, which can be found with the documentation at https://octopus.com/docs/support/log-files. These logs may have more details that resulted in the bad request.
Now we are getting octo.exe error
2018-09-25T02:43:04.3139910Z ##[section]Starting: Create Octopus Release:
2018-09-25T02:43:04.3145478Z Task : Create Octopus Release
2018-09-25T02:43:04.3145612Z Description : Create a Release in Octopus Deploy
2018-09-25T02:43:04.3145770Z Version : 2.0.135
2018-09-25T02:43:04.3145888Z Author : Octopus Deploy
2018-09-25T02:43:04.3146055Z Help : Version: 2.0.135. More Information
2018-09-25T02:43:09.1456260Z ##[command]“D:\a_tasks\OctopusCreateRelease_4e131b60-5532-4362-95b6-7c67d9841b4f\2.0.135\Octo.exe” create-release --project=“Smart_Service.ERollOff” --releaseNumber="" --channel="" --server=https://abacusdsm-2109.octopus.accenture.com/Abacus_Shared --apiKey=*** --enableServiceMessages --deployTo=“Smart_10054_Dev” --progress --releaseNotesFile=“D:\a\28\s\release-notes-44b4da71-a8b5-4fb4-985b-93bb832eedd9.md”
2018-09-25T02:43:09.8570207Z Octopus Deploy Command Line Tool, version 4.34.0
2018-09-25T02:43:10.6632182Z Handshaking with Octopus server: https://abacusdsm-2109.octopus.accenture.com/Abacus_Shared
2018-09-25T02:43:10.6634869Z Handshake successful. Octopus version: 2018.6.5; API version: 3.0.0
2018-09-25T02:43:10.7470737Z Authenticated as: Mishra, Mili firstname.lastname@example.org
2018-09-25T02:43:10.7527996Z This Octopus Server supports channels
2018-09-25T02:43:10.7528356Z Finding project:
2018-09-25T02:43:10.9781312Z Automatically selecting the best channel for this release…
2018-09-25T02:43:11.0420827Z Building a release plan for Channel ‘Default’…
2018-09-25T02:43:11.0470908Z Finding deployment process…
2018-09-25T02:43:11.1194219Z Finding release template…
2018-09-25T02:43:11.1888945Z Channel Default does not contain any packageSteps
2018-09-25T02:43:11.2240434Z There are no viable release plans in any channels using the provided arguments. The following release plans were considered:
2018-09-25T02:43:11.2240762Z Channel: ‘Default’ (this is the default channel)
2018-09-25T02:43:11.2241874Z This error is most likely ocurring while executing Octo.exe as part of an automated build process. The following doc is recommended to get some tips on how to troubleshoot this: https://g.octopushq.com/OctoexeTroubleshooting
2018-09-25T02:43:11.2242135Z Exit code: -1
2018-09-25T02:43:11.5898375Z ##[error]Process ‘Octo.exe’ exited with code ‘-1’.
2018-09-25T02:43:11.6022327Z ##[section]Finishing: Create Octopus Release:
An unexpected error occurred while attempting to retrieve and execute a task: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. System.Data.SqlClient.SqlException (0x80131904): Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
Just seen this after creating another post. Same deal for us since this morning i notice extension was last updated midnight last night ?
We have had a few reports of this issue, and created a GitHub issue at https://github.com/OctopusDeploy/OctoTFS/issues/107 to track the progress. We’ll update the issue when we find the underlying cause, so keep an eye on that.
Others have mentioned that disabling changeset and work items has worked for them, so that might be a valid workaround for now.
If you have any other information, please feel free to add a comment to the GitHub issue, as this will be the central location where we track the progress.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.