Hey,
Since upgrading to Octopus Deploy v3.15.7, we’re getting a weird error when trying to view details of packages included in a release - see the attached screenshot for details.
Any ideas what’s causing this or how we can fix it?
Thanks!
-D-
Hi Dylan,
This usually happens when we can’t read the metadata of the package.
What Octopus Server version were you on before ?
What kind of feed are these packages coming from ? is it TeamCity, nuget, internal feed, local folder ?
Can you also send us the server logs, https://octopus.com/docs/reference/log-files#Logfiles-Findingthelogfiles
If you were on a version prior to 3.4, there is a breaking change in the way we read packages from TC, see Download: 3.4.0 - Octopus Deploy
Breaking change: If you are using TeamCity NuGet feeds you will need to upgrade to TeamCity 9.0 or newer (Recommend latest due to continual improvements in NuGet feed) or switch to using the Octopus built-in repository. This is due to upgrading our NuGet dependencies to v3 which aren’t compatible with the custom v1 feed provided by TeamCity 7.x-8.x. We recommend upgrading to the latest TeamCity version and enabling the v2 NuGet feed API.
Cheers
John
Yep, it was a NuGet v1/v2 problem - we host our packages on an internal server running Klondike (https://github.com/themotleyfool/Klondike), and we had to update the Package Feeds endpoint to http://klondike/api/odata instead of just http://klondike/ to force it to use the NuGet v2 API.
Thanks!
Hi Dylan,
No problem, let us know if there is any other issues.
Cheers
John