This occurs on every release and I am not able to determine when this began. We host our own Klondike server and package .nupkg files.
Again, this is not blocking us because he packages exist AND the deployments succeed. However, the error is very misleading and causing confusion for our engineers and QA. (See attached image)
Hi,
Thanks for getting in touch. Can you let me know what version of Octopus you are running and what version of Klondike you are running?
Also do you know if you only see this with some packages and versions or all? Certainly some nuget feeds handle trailing ‘0’ in package versions differently.
Regards,
Mark
Thanks for the quick response, Mark.
Klondike version: v1.6.2
Octopus: 3.11.13
We have hundreds of releases and I’ve been vigorously spot checking and every one I’ve seen throws the 404 error. Not a definitive answer but each one I’ve checked has either been deployed, or was able to be deployed, successfully.
Hope this helps.
Thanks,
Ryan
Hi Ryan,
In 3.11.8 we changed how we query for the release notes (which is the query you see failing here) to use a different API endpoint on the Nuget server, to make things more efficient. I’ll install Klondike and take a look at what is going on. Different Nuget server implementations can behave pretty differently unfortunately. We only use this endpoint for these release notes which is why the rest of your deployment process should still be working fine.
Regards,
Mark
Hi Ryan,
It looks like there is some incompatibility between Klondike and the version of the Nuget libraries we are using. Can you try changing your Klondike feed address in Octopus from http://your.klondike.server/api to http://your.klondike.server/api/odata. That resolved things in my testing.
Regards,
Mark
Thanks Mark! That fixed it!
Cheers!
Ryan