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

User Role saving blocked by validation error #5701

Closed
NickJosevski opened this issue Jul 15, 2019 · 2 comments
Closed

User Role saving blocked by validation error #5701

NickJosevski opened this issue Jul 15, 2019 · 2 comments
Assignees
Labels
kind/bug This issue represents a verified problem we are committed to solving
Milestone

Comments

@NickJosevski
Copy link

The bug

A validation error prevents saving User Roles where that User Role contains invalid permissions. Impacts a small set of User Roles that were not correctly migrated in 2019.1

What I expected to happen

The User Role should be able to be modified

Steps to reproduce

  1. Find a User Role that that has space only permissions in the system set, or system only permissions on the space set.
  2. Modify the name (or anything) and try to save

Screen capture

image

Log exerpt

There was a problem with your request.
The following are not valid Space permissions: SpaceEdit, SpaceView, SpaceDelete, SpaceCreate.

Affected versions

2019.1 to current, including LTS

Octopus Server:

Workarounds

Make use of a different / newly created user role that you can set up correctly, until this is patched.

Links

  • NA
@NickJosevski NickJosevski added the kind/bug This issue represents a verified problem we are committed to solving label Jul 15, 2019
@NickJosevski
Copy link
Author

Release Note: Fix for incorrectly migrated user roles that could not be saved due to validation error

@lock
Copy link

lock bot commented Oct 15, 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 Oct 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Development

No branches or pull requests

2 participants