Project Process displaying error after Upgrade to Octopus v2018.9.5

lee.zhou · 7 November 2018 15:46

Hello,

We have recently upgraded from Octopus 4.1.9 to the latest Octopus v2018.9.5, and encountering the following error for one of our projects:

An unexpected error occurred in Octopus v2018.9.5: “TypeError: Cannot read property ‘PackageId’ of undefined”

in t
in div
in div
in div
in div
in t
in div
in div
in div
in div
in div
in div
in l
in div
in t
in div
in div
in n
in n
in Connect(n)
in t
in t
in t
in t
in t
in t
in div
in div
in MediaQuery
in div
in w
in t
in withRouter(w)
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

Exception

Octopus v2018.9.5

TypeError: Cannot read property ‘PackageId’ of undefined render (/app/components/Actions/iis/iisAction.tsx:31:53) 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) 0;null!==a&&c;){c=!1;if(a.pendingWorkPriority===T||a.pendingWorkPriority>b)c=!0,a.pendingWorkPriority=b;null!==a.alternate&&(a.alternate.pendingWorkPriority===T||a.alternate.pendingWorkPriority>b)&&(c=!0,a.alternate.pendingWorkPriority=b);if(null===a[“return”])if (/node_modules/react-dom/cjs/react-dom.production.min.js:188:389) S (/node_modules/react-dom/cjs/react-dom.production.min.js:187:415) enqueueSetState (/node_modules/react-dom/cjs/react-dom.production.min.js:140:181) isMounted (/node_modules/react/cjs/react.production.min.js:12:343)

Any idea to resolve this, or should we look into reverting back to the 4.1.9 version?

lee.zhou · 7 November 2018 16:50

Issue resolve by reviewing the export project deployment steps and finding the step that required a package, but was disabled prior to the upgrade.

You can close the ticket.

Kenneth_Bates · 8 November 2018 00:02

Hi Lee,

Thanks for getting in touch! That’s great to hear you’ve been able to resolve this issue - thank you for letting us know the outcome. Please don’t hesitate to reach out if you have any further questions or concerns moving forward!

Best regards,

Kenny

Silas_Hansen1 · 7 December 2018 11:32

We also have this issue and thus no way to way edit any of the steps to try and resolve the issue as this error is blocking the entire view.

It happens when we open a project and click “Process”.

Can you guide us in the direction of what to do?

nick · 9 December 2018 23:29

Hi Silas,

Thanks for getting in touch, sorry to hear you’re having a similar issue. Could you give us some more information as to what version you’re on and what kind of package steps are part of your deployment process.

We recently fixed a problem that was related to Java package steps, if you have those as part of your deployment process and are not yet on 2018.9.13 an upgrade may resolve this problem, this is the associate issue.

Because others have already commented on this issue I can’t make it private, we may be able to resolve this more quickly if we can get a hold of your deployment process. Even though the page crashes the API request and response will be in the network tab of your browsers developer tools. If you could send through all the text of response to the api/deploymentprocess calls that will be really helpful.

Have a look at this screenshot of what to look for, you can select all the text and save it in a text file to send. If it has anything sensitive or you don’t want to be public, you can email it through to support@octopus.com

Regards,
Nick

Silas_Hansen1 · 12 December 2018 11:45

For anyone wondering, this was solved by the Octopus support team through private email.

It basically involves running a custom script against the Octopus API to find and insert the packageId in the step where it’s missing.

Nick has the code to do that.

system · 11 January 2019 11:45

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