Azure ARM Step template select Exeption

Legacy Modelling
1

Getting the following exception when adding the ARM step template in Octopus Cloud:Octopus v2018.8.1

TypeError: Cannot read property ‘FeedId’ of undefined

render (/app/components/Actions/azureResourceGroup/azureResourceGroupAction.tsx:178:64)
predicate (/node_modules/lodash/lodash.js:823:0)
toInteger (/node_modules/lodash/lodash.js:7275:0)
predicate (/node_modules/lodash/lodash.js:5098:0)
render (/app/components/Actions/azureResourceGroup/azureResourceGroupAction.tsx:178:23)
Lf (/node_modules/react-dom/cjs/react-dom.production.min.js:147:337)
sf:a:{e=b.type;c=b.pendingProps;d=b.memoizedProps;if(nf())null===c&& (/node_modules/react-dom/cjs/react-dom.production.min.js:150:232)
e (/node_modules/react-dom/cjs/react-dom.production.min.js:182:349)
g (/node_modules/react-dom/cjs/react-dom.production.min.js:183:347)
p (/node_modules/react-dom/cjs/react-dom.production.min.js:184:366)

3

Hi Anton,

Thanks for getting in touch! I’m terribly sorry you’re hitting this annoying and unexpected bug with the ARM step template. Fortunately it’s already a known issue which has been fixed in version 2018.8.2. Would you be able/willing to upgrade and let me know if this fixes the issue for you? You can refer to the issue here.

I hope this helps! Let me know how you go or if you have any further questions. :slight_smile:

Best regards,

4

Hi Kenneth,

I am aware that this is a bug that has been resolved in version 2018.8.2 that is why I added it to my request.

I am totally willing to upgrade to the latest version, problem with that unfortunately is that we are running it in the cloud, and therefore upgrading should be part of the package, and dealt with by you guys.

Please correct me if I am wrong, or share the steps to upgrade to the latest version with me and I will be happy to press the button.

Kind Regards,

Anton

5

Hi Anton,

Thanks for following up, and I’m sorry about the confusion here. I can certainly upgrade your hosted instance to include this fix. I’ve triggered the upgrade to 2018.8.3 to occur during your next maintenance window, so you should receive the fix soon.

I’m terribly sorry about the inconvenience we’ve caused with this bug. Please don’t hesitate to reach out if you have any further questions moving forward. :slight_smile:

Best regards,

Kenny

6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.