Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server fails to start as part of upgrading to 2019.2.5 #5414

Closed
NickJosevski opened this issue Mar 21, 2019 · 2 comments
Closed

Server fails to start as part of upgrading to 2019.2.5 #5414

NickJosevski opened this issue Mar 21, 2019 · 2 comments
Assignees
Milestone

Comments

@NickJosevski
Copy link

NickJosevski commented Mar 21, 2019

The bug

For a small set of customers, with specifically misconfigured UserRoles the upgrade to 2019.2.5 would fail with an exception, preventing Octopus from starting up.

This bug does not cause data corruption, it simply blocks the startup of the server.

Log exerpt

ERROR  Upgrade failed due to an unexpected exception:
System.ArgumentNullException: Value cannot be null.
Parameter name: value
   at Newtonsoft.Json.Linq.Extensions.Value[T,U](IEnumerable`1 value)
   at Octopus.Core.UpgradeScripts.Script0001RemoveTaskViewLogPermissionAgain.UserRoleData.get_GrantedSpacePermissions()
   at Octopus.Core.UpgradeScripts.Script0001RemoveTaskViewLogPermissionAgain.RoleNeedsUpgrading(UserRoleData role)

Affected versions

Octopus Server: 2019.2.5 only (which is no longer available for download)

Workarounds

Update to 2019.2.6

@NickJosevski NickJosevski added this to the 2019.2.6 milestone Mar 21, 2019
@NickJosevski NickJosevski self-assigned this Mar 21, 2019
@NickJosevski
Copy link
Author

Release Note: Fixed startup issue for a subset of customers by a data consistency script in 2019.2.5

@lock
Copy link

lock bot commented Jun 25, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant