Deleting an Octopus Server Node Fails

reliability
(kshanafelt) #1

Deleting an Octopus Server Node produced that following error:

An unexpected error occurred in Octopus v2019.3.5: The link is not set to a value

Error: The link is not set to a value
e.resolve (http://octopus.paraport.com/main.0dc9f5596a5ebbe8edf6.hashedasset.js:1:772249)
t.del (http://octopus.paraport.com/main.0dc9f5596a5ebbe8edf6.hashedasset.js:1:1244361)
t.del (http://octopus.paraport.com/main.0dc9f5596a5ebbe8edf6.hashedasset.js:1:101547)
n. (http://octopus.paraport.com/main.0dc9f5596a5ebbe8edf6.hashedasset.js:1:3896338)
http://octopus.paraport.com/main.0dc9f5596a5ebbe8edf6.hashedasset.js:1:3890180
Object.next (http://octopus.paraport.com/main.0dc9f5596a5ebbe8edf6.hashedasset.js:1:3890285)
http://octopus.paraport.com/main.0dc9f5596a5ebbe8edf6.hashedasset.js:1:3889198
http://octopus.paraport.com/vendor.162da54cfd8cb21a5b6e.hashedasset.js:70:3827
new W (http://octopus.paraport.com/vendor.162da54cfd8cb21a5b6e.hashedasset.js:70:3887)
o (http://octopus.paraport.com/main.0dc9f5596a5ebbe8edf6.hashedasset.js:1:3888981)

Looking the browser’s developer tools it looks like it is attempting to call Links.Self on an object that looks like this (Note: it has a Links.Node, but no Links.Self):

{
   "Id" : "OctopusServerNodes-Example-06",
   "IsInMaintenanceMode" : true,
   "IsLeader" : false,
   "IsOffline" : false,
   "LastSeen" : "2019-06-27T02:49:07.722+00:00",
   "Links" : {
     "Node" : "/api/octopusservernodes/OctopusServerNodes-Example-06", 
     "Details" : "/api/octopusservernodes/OctopusServerNodes-Example-06/details"
   },
   "MaxConcurrentTasks" : 10,
   "Name" : "Example-06",
   "Rank" : "Follower",
   "RunningTaskCount" : 0
}

Sending a delete request using the value in the Links.Node via postman, works as a workaround (Just remember to set X-Octopus-ApiKey in the header)

(kshanafelt) #2

Looks like this has already been fixed in 2019.5.0 see “Link not set to a variable” error when deleting offline HA Node on GitHub.

We are on version 2019.3.5 LTS.

Is there a time-line for when these types of bug fixes get rolled into the Long Term Support version?

(Dalmiro Grañas) #8

Hi @kshanafelt,

Thanks for reaching out. Yes as you have pointed out, that bug has already been fixed. We’ll be releasing 2019.6.x LTS mid-next-week which will include this fix.

Best regards,
Dalmiro