Error renaming tag in Tenant Tag Set which was in use


(claire.furney) #1

I renamed a tag in an existing tenant tag set on the Library > Tenant Tag Sets page. The tag was already in use on a Project Step as well as against a Tenant. I was hoping the new name would just filter through, but instead when trying to load up the “Tenants” screen I was faced with an error and the screen didn’t load. (I worked around by removing the tag, renaming it, then readding it).

Screenshot of error:

Full exception details (from Show Full Exception):

Octopus v2018.7.6
d/<.content<@https://octopus.server/tenants.1a74718cf54e3289cab8.hashedasset.js:1:4027
description (/app/areas/tenants/TenantCard/TenantCard.tsx:33:20)
tenant (/app/areas/tenants/TenantCard/TenantCard.tsx:31:16)
beginWork (/node_modules/react-dom/cjs/react-dom.production.min.js:149:336)
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)
m (/app/components/BaseComponent/BaseComponent.tsx:29:8)
componentDidMount (/app/areas/tenants/Tenants/Tenants.tsx:66:12)
step (webpack:///tenants.1a74718cf54e3289cab8.hashedasset.js:705:17)
verb (webpack:///tenants.1a74718cf54e3289cab8.hashedasset.js:686:52)
fulfilled (webpack:///tenants.1a74718cf54e3289cab8.hashedasset.js:677:47)
tryCatch (/node_modules/es6-promise/dist/es6-promise.js:410:0)
isFunction (/node_modules/es6-promise/dist/es6-promise.js:425:0)
publish (/node_modules/es6-promise/dist/es6-promise.js:393:0)
flush (/node_modules/es6-promise/dist/es6-promise.js:121:0)


(Daniel Fischer) #3

Hi @claire_furney,

Thanks for getting in touch! It looks like you have run into the following issue:

It looks like we released a fix for this in Octopus version 2018.8.5. Upgrading to at least this version should stop you from encountering this problem. :slight_smile:

Let me know if you have any further thoughts or questions here.

Best regards,
Daniel


(claire.furney) #4

Thanks for the confirmation Daniel. We’re currently on v2018.7.6 so makes sense.


(Daniel Fischer) #5

Hi @claire_furney,

Thanks for the update! Please feel free to get in touch at any time. :slight_smile:

Best regards,
Daniel


(system) #6

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