Hi Support,
We’re using Octopus 3.17.2 and running an old job fails:
Starting: Publish octopus package
Task : Push Package(s) to Octopus
Description : There is a later version of this task, we recommend using the latest version. Push your NuGet or Zip package to your Octopus Deploy Server
Version : 4.3.134
Author : Octopus Deploy
Help : Version: 5.2.134. More Information
==============================================================================
##[warning]There is a later version of this task, we recommend using the latest version.
C:\WINDOWS\system32\cmd.exe /D /S /C “C:\agent_work_tool\octo\7.4.3663\x64\octo.cmd version”
Detected automation environment: “AzureDevOps”
System.InvalidOperationException: The character set provided in ContentType is invalid. Cannot read content as string using an invalid character set. —> System.ArgumentException: ‘“UTF-8”’ is not a supported encoding name. For information on defining a custom encoding, see the documentation for the Encoding.RegisterProvider method.
Parameter name: name
at System.Globalization.EncodingTable.internalGetCodePageFromName(String name)
at System.Globalization.EncodingTable.GetCodePageFromName(String name)
at System.Text.Encoding.GetEncoding(String name)
at System.Net.Http.HttpContent.ReadBufferAsString(ArraySegment`1 buffer, HttpContentHeaders headers)
It ran last time succeeding with:
Starting: Publish octopus package
Task : Push Package(s) to Octopus
Description : Push your NuGet or Zip package to your Octopus Deploy Server
Version : 4.2.492
Author : Octopus DeployDetected automation environment: “AzureDevOps”
Process will run in backwards compatible mode for older versions of Octopus Server
Handshaking with Octopus Server: http://mp-cd-01/
Handshake successful. Octopus version: 3.17.2; API version: 3.0.0
Authenticated as:
Pushing package: C:\agent_work\5\a\drop\ProfileUpdate.20211125.1.zip…
Server does not support delta compression for package push
Falling back to pushing the complete package to the server
Push successful
I’ve found similar issues:
Is there a way to revert back to 4.2, or is it possible to update octo.cmd without upgrading?
We’d really appreciate advice on a way forward to overcome this error? Thanks. Any more info please let me know.