Deploy an Azure Resource Group Template Crashing

We use the “Deploy an Azure Resource Group” template built by Octopus to deploy to Azure. However since updating to version 2018.8.0 this step now shows an error when you try to edit it.

This is obviously pretty critical for us to get resolved.

To reproduce; go to a project, click add step, select the “Deploy an Azure Resource Group” template and the error will appear. Or in our case edit this step in an existing project.

Full exception below:

Octopus v2018.8.0

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)

An unexpected error occurred in Octopus v2018.8.0: “TypeError: Cannot read property ‘FeedId’ of undefined”
in t
in t
in div
in div
in div
in t
in div
in div
in t
in div
in div
in n
in div
in t
in div
in t
in t
in t
in withRouter(t)
in t
in Connect(t)
in n
in t
in t
in t
in t
in t
in t
in div
in div
in MediaQuery
in div
in S
in t
in withRouter(S)
in main
in t
in Connect(t)
in t
in t
in t
in t
in t
in t
in withRouter(t)
in t
in t
in t
in t
in t
in r
in t
in t
in t
in t
in t
in x
in div
in t
in Connect(t)
in t
in t
in t
in t
in t
in t
in t
in t
in Provider
in t
in i
in t

+1

Running existing ARM task works still, but creating a new Step Template based on the built in task gives me the same error that @tonyschollum gets. We’re using Octopus Cloud.

Hi Tony,

Thanks for getting in touch! I’m terribly sorry you’re hitting this annoying bug. I understand it can be very frustrating. Fortunately this is already a known issue, and we pushed a fix for it in 2018.8.2. You can reference the issue here.

https://github.com/OctopusDeploy/Issues/issues/4856

Would you be willing to upgrade to latest and let us know if this fixes the issue for you?

Best regards,

Kenny

Hi Kenny,

Thanks for the quick response, yes the upgrade to 2018.8.2 has resolved the issue.

Cheers!

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