An unexpected error occurred in Octopus v2018.12.1: Cannot read property 'split' of undefined

Hi Octopus Support,

When using the Deploy Kubernetes step in our projects, we can edit all of the options except “Add Volume.” When selecting Add Volume, we receive the below error. The only workaround is to completely remove the step and re-add it, even if all we want to do is add another volume.

An unexpected error occurred in Octopus v2018.12.1: Cannot read property ‘split’ of undefined

** TypeError: Cannot read property ‘split’ of undefined*
** n.<anonymous> (https://octopus/main.b5477bc9a2d1cccfe430.hashedasset.js:1:4850614)*
** https://octopus/main.b5477bc9a2d1cccfe430.hashedasset.js:1:4848162*
** (https://octopus/main.b5477bc9a2d1cccfe430.hashedasset.js:1:4848267)*
** s (https://octopus/main.b5477bc9a2d1cccfe430.hashedasset.js:1:4847013)*
** https://octopus/vendor.8135177baaf935bd0bdf.hashedasset.js:70:2822*
** F (https://octopus/vendor.8135177baaf935bd0bdf.hashedasset.js:70:2856)*
** N (https://octopus/vendor.8135177baaf935bd0bdf.hashedasset.js:70:2636)*
** MutationObserver.g (https://octopus/vendor.8135177baaf935bd0bdf.hashedasset.js:70:671)*

Hi Alex,

Thanks for getting in touch! I’m terribly sorry you’re hitting this strange and inconvenient issue. I actually haven’t been able to reproduce this behavior in my local instance running 2019.2.8. Would you be able and willing to upgrade and let me know if this issue gets resolved?

I don’t see a specific issue of this getting resolved, so I suspect it was fixed in conjunction with another bug fix around the Kubernetes step.

I hope this helps! Please let me know how you go or if you have any further questions or concerns moving forward. :slight_smile:

Best regards,


Hi Kenneth,

Thank you for your response. We did recently upgrade our test server to Octopus 2018.12.1 (partly because we saw there were a number of breaking changes and permission changes with 2019 versions). We were hoping to resolve the Kubernetes issues on this version.

If the only solution is another upgrade, we might go with 2019.3.0 as it’s recommended in the slow-lane. Have you noticed any major issues with that version from users (permissions, Kubernetes, etc.)? Would we get additional support with the slow-lane LTS version?

Thank you,


Hi Kenneth,

We just upgraded to Octopus v2019.3.1 LTS version, and we are getting the same error editing volumes.

Do you have any recommendations at this point for resolution now that we are on a supported version?

EDIT: We are on v2019.3.2–Recommended Version. Same issue.



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