AAP-54064 clear RBAC data in migration step #1771
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is split from #1770 to be the minimum changes to facilitate the fix.
Jira Issue: https://issues.redhat.com/browse/AAP-54064
Assisted-by: Claude (kind of, it wasn't that much help for this)
Description
Without this, we can hit an upgrade error for the 2.5->2.6 line. This is because of the DAB 2.5 behavior of auto-registering the
Team
model. No models are intended to be registered, and you can see this in the setting in thebase.py
settings module. So there is no hazard in delete all rows in RBAC, as this does. RBAC is intended to be enabled and also unused and we will continue with that expectation.Testing
TBD - do upgrade testing
Steps to test
Do full deployments in OCP, I don't have a local or minimal version of the fix. Although it would be possible.
Scenarios tested
TBD
Production deployment
Needs testing in production.