We are getting an error " “TypeError: Cannot read properties of undefined (reading ‘Properties’)”" while accessing the process configuration in a project. It has the configuration to extract a package and upload it to the s3 bucket. We are using the inbuilt s3 sync plugin.
The whole setup is created with Terraform. From the error, we understand that it is something related to the property attribute. So pasting the all properties that we pass to the resource from Terraform.
Terraform apply is working as expected and it is successful but while we try to access the process configuration from the console we are getting this error.
Please have a look.
========= The complete error message=======
An unexpected error occurred in Octopus v2023.3.6319-hotfix.6572: "TypeError: Cannot read properties of undefined (reading 'Properties')"
in AwsUploadS3ActionEditInternal
in default
in s
in sl
in div
in div
in div
in TransitionAnimation
in div
in div
in PaperLayout
in Uy
in ExpandableContainer
in ProcessActionDetailsInternal
in ProcessActionDetails
in c
in DatabaseComponentContextProvider
in FieldErrorContextProvider
in ErrorContextProvider
in RenderWithPage
in EnhancedProcessActionDetailsPage
in div
in t
in ForwardRef
in div
in div
in ProcessSidebarLayout
in div
in TransitionAnimation
in div
in div
in PaperLayout
in div
in KeyboardHandler
in div
in FormComponent
in i
in FormPaperLayoutInternal
in Unknown
in withRouter()
in ProjectContextFormPaperLayout
in DeploymentsProcessEditorFormPaperLayout
in ProcessContextFormPaperLayout
in withRouter(ProcessContextFormPaperLayout)
in ProcessWarningActions
in ProcessErrorActions
in ProcessStepsLayout
in EnhancedProcessStepsLayout
in ProcessQueryStringController
in Unknown
in Unknown
in ProcessSearchFilterController
in c
in $u
in u
in ProcessController
in ProcessStepsLayoutLoader
in DataBaseComponent
in Unknown
in ProcessStepsLayoutDataLoader
in WithProjectDeploymentProcess
in c
in DatabaseComponentContextProvider
in FieldErrorContextProvider
in ErrorContextProvider
in RenderWithPage
in t
in t
in DatabaseComponentContextProvider
in FieldErrorContextProvider
in ErrorContextProvider
in BranchAwareRedirectInternal
in BranchAwareRedirect
in ProcessRoute
in withRouter(ProcessRoute)
in t
in t
in ErrorBoundaryInternal
in ReloadableRoute
in DeploymentsRoute
in withRouter(DeploymentsRoute)
in t
in ErrorBoundaryInternal
in ReloadableRoute
in t
in ErrorBoundaryInternal
in RouteAwareErrorBoundary
in div
in div
in i
in t
in j
in Unknown
in div
in NavigationSidebarLayout
in withRouter(NavigationSidebarLayout)
in main
in ProjectContextProvider
in ProjectLayoutInternal
in DatabaseComponentContextProvider
in FieldErrorContextProvider
in ErrorContextProvider
in jT
in SlugSafeRedirect
in withRouter(SlugSafeRedirect)
in t
in ErrorBoundaryInternal
in ReloadableRoute
in t
in ProjectRoutes
in t
in ErrorBoundaryInternal
in ReloadableRoute
in t
in t
in Suspense
in RootRoutes
in withRouter(RootRoutes)
in SpaceLoader
in WithPersistedSpace
in Connect(WithPersistedSpace)
in withRouter(Connect(WithPersistedSpace))
in div
in StandardLayoutInternal
in Connect(StandardLayoutInternal)
in t
in ErrorBoundaryInternal
in ReloadableRoute
in SecureRoute
in t
in l
in i
in i
in l
in u
in Q
in div
in rf
in QO
in t
in t
in aT
in DevToolsContextProvider
in ClientConnector
in l
in S
in iT
in PageProvider
in F
in DatabaseComponentContextProvider
in FieldErrorContextProvider
in ErrorContextProvider
in ErrorBoundaryInternal
in l
in d
in id
in App
Thank you for contacting Octopus Support and sorry to hear you are seeing errors when trying to access the process configuration in a project.
It seems you are on our Octopus Cloud offering with your instances URL being https://stayntouch.octopus.app/ is that correct?
If so would you mind if we created a Support user on your instance please so we can take a look at this for you, you don’t have to do anything your end to create the Support user, we just need your explicit permission.
If you can give us an idea of the project name too just so we can find it quickly that would be great.
I was able to log in to your instance and access the project and all sub-pages within the project without error.
Would you be able to link the page you’re experiencing the error on, please?
We’ll bring this to the attention of our engineers immediately who can investigate further.
Would you mind if one of our engineers accessed your instance for troubleshooting purposes?
Thank you for getting back to us and requesting an update, the engineers started to look at this issue a few hours ago but it was nearing the end of their working day unfortunately. They are based in Australia so when you reported this issue on Friday they had already left for their weekend so they picked this up last night when they were back in work (their Monday morning).
They have not managed to replicate this issue themselves so they think this is specific to your instance which sounds right considering what Adam found on Friday.
The engineers will continue to look at this for you when they get back to work tonight and we will get an update out to you once we have one.
I am sorry this is still causing you frustration but it does look like its specific to your instance so the engineers would need to take a look at your instance specifically and the backend database to see what the issue is.
We will keep you updated as soon as we know anything, reach out in the meantime if you have any other questions or notice other issues and we will do our best to help.
Could you please confirm how you are creating this project in Terraform? I have a feeling it might be due to using step.action.package which defines a name instead of step.action.primary_package which just uses the packageId but I’ll dig into it some more and see what improvements we could make to it.
Looking forward to hearing how you get on, feel free to reach out with any questions at all!
Please ignore my previous comment. This is fixed when I destroy the whole settings and reapplied the Terraform workspace. But not sure why it is not applied with the existing configurations in place. I doubt we can do the same in future for issues similar to this.
It seems like the error is gone and I can see the process configurations. I thank all of you for your support.
