Cannot add a new listening tentacle on 2019.4.1

[mattjeanes23]

Not sure if this is caused by my downgrade from 2019.5.4 (see Octopus will not start after upgrading to 2019.5.4 from 2019.4.1) but shouldn’t be as it’s a clientside typescript error.

Debugging the tsx file it looks like in the buildTentacleEndpointHealthCheckHtml method in MachinePolicySummary.tsx the TentacleEndpointHealthCheckPolicy property of policy is null.

I was able to work around the issue by running this in the debugger while it was paused in that function: this.props.machinePolicy.MachineHealthCheckPolicy.TentacleEndpointHealthCheckPolicy = {RunType:"InheritFromDefault"}; this.props.machinePolicy.MachineHealthCheckPolicy.SshEndpointHealthCheckPolicy = {RunType:"InheritFromDefault"};

Octopus v2019.4.1

TypeError: Cannot read property 'RunType' of null

buildTentacleEndpointHealthCheckHtml (/app/areas/infrastructure/components/MachinePolicySummary/MachinePolicySummary.tsx:143:78)
render (/app/areas/infrastructure/components/MachinePolicySummary/MachinePolicySummary.tsx:49:50)
Yg (/node_modules/react-dom/cjs/react-dom.production.min.js:169:128)
Wg (/node_modules/react-dom/cjs/react-dom.production.min.js:168:256)
b.tag=0,S (/node_modules/react-dom/cjs/react-dom.production.min.js:176:0)
hi (/node_modules/react-dom/cjs/react-dom.production.min.js:221:15)
ii (/node_modules/react-dom/cjs/react-dom.production.min.js:222:280)
Ki (/node_modules/react-dom/cjs/react-dom.production.min.js:238:232)
Li (/node_modules/react-dom/cjs/react-dom.production.min.js:237:142)
fi (/node_modules/react-dom/cjs/react-dom.production.min.js:234:195)

[henrik (Henrik Andersson)]

Hi Matt,

This will have been caused by the upgrade and then downgrade as there were database scripts that modified the data in the database. Our guidelines for moving between major or minor versions is to take a database backup before the upgrade in case it goes wrong and a downgrade is required.

As creating a database script to fix up any data that has been changed is more likely to cause further issues, we’ll work on figuring out what caused the error you were seeing after upgrading to 2019.5.4 in your other ticket.

Thank you and best regards,
Henrik

[mattjeanes23]

Okay, that’s fine - just wanted to make sure. You can close this topic if there is such a thing