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.

Sign up for GitHub

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

Jump to bottom

[BUG] Issues with Jobs (or other objects) that have no OWNER #73

Closed
renardeinside opened this issue Aug 9, 2023 · 0 comments · Fixed by #485
Closed

[BUG] Issues with Jobs (or other objects) that have no OWNER #73

renardeinside opened this issue Aug 9, 2023 · 0 comments · Fixed by #485
Assignees
@william-conti
Labels
migrate/groups Corresponds to Migrate Groups Step of go/uc/upgrade

Comments

@renardeinside
Copy link
Contributor

renardeinside commented Aug 9, 2023 •
edited
Loading

In some customer environments the permission application step is failing because of absence of the OWNER on the object.

Such situations can happen when user who is owner of a group has been deleted.

Proposed fix - collect the problematic objects into a separate list, and then provide a warning message saying that these objects require an owner property prior to migration.
@renardeinside renardeinside changed the title Issues with Jobs (or other objects) that have no owner ]Issues with Jobs (or other objects) that have no owner Aug 9, 2023
@renardeinside renardeinside changed the title ]Issues with Jobs (or other objects) that have no owner [BUG] Issues with Jobs (or other objects) that have no OWNER Aug 9, 2023
@nfx nfx added the enhancement New feature or request label Sep 18, 2023
@nfx nfx added this to the 3 months milestone Sep 18, 2023
@nfx nfx added bug and removed enhancement New feature or request labels Sep 25, 2023
@pohlposition pohlposition added the migrate/groups Corresponds to Migrate Groups Step of go/uc/upgrade label Sep 28, 2023
@william-conti william-conti mentioned this issue Oct 20, 2023
Merged
@william-conti william-conti self-assigned this Oct 24, 2023
@nfx nfx closed this as completed in #485 Oct 27, 2023
nfx pushed a commit that referenced this issue Oct 27, 2023
@william-conti
Fixing assessment throwing an error when the owner of an object is em…
ebf66ad 
…pty (#485)

Fixes #73

By default, all objects without owners will have their created_by column
persisted as an empty string instead of null/None for the sake of
backward compatibility.

It also adds Integration tests for the SQLBackend in order to harden the
code
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@william-conti william-conti

Labels
migrate/groups Corresponds to Migrate Groups Step of go/uc/upgrade
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fixing assessment throwing an error when the owner of an object is empty databrickslabs/ucx
4 participants
@nfx @renardeinside @pohlposition @william-conti