Attempts To Delete An Immuta Schema Project Fail
Removal of an Immuta Schema Project is failing reporting the error “The only remaining owner cannot unsubscribe, expire, or be removed.”
Last updated
Support Knowledge Articles
Removal of an Immuta Schema Project is failing reporting the error “The only remaining owner cannot unsubscribe, expire, or be removed.”
Last updated
The following knowledge base article examines one scenario where the configuration for a Schema Project and its owners can result in the failure of attempts to remove the project once it is no longer required. There may be other conditions under which the error can appear.
The proposed scenario below is known to cause the problem and to demonstrate conditions which result in a Schema Project deletion failure.
Multiple Schema Project owners exist for the Schema Project "PLB2023 Public".
Paul Burgess is the original Schema Project owner and built the Snowflake Integration and the associated data sources.
A new user plb was added to Immuta as an additional owner and is a user and project management admin level user in Immuta.
Attempts to delete the Schema Project are failing reporting the following error:
The conditions and events occurring that result in problems deleting the schema project using the Immuta UI.
The error has been seen to occur when the following sequence of events has appeared in Immuta, there may be others.
An integration has been added as one Immuta User, xxxxx@immuta.com.
The datasource(s) have/has been added as xxxxx@immuta.com.
A new user, plb, is added to Immuta with the following minimum set of Immuta privileges. CREATE_DATA_SOURCE_IN_PROJECT,CREATE_PROJECT,CREATE_DATA_SOURCE,AUDIT, USER_ADMIN
The new user, plb, is added to the schema project, PLB2023 Public, as an owner.
A login as the original owner, xxxxx@immuta.com, and editing the schema project Schema Monitoring and setting of the new user, plb, as the schema monitoring user.
A login as the new user, plb, occurs and the original owner, xxxxx@immuta.com, is set to be a subscriber only.
Setting of the project schema monitoring user to the original owner, xxxxx@immuta.com (now a subscriber only) occurs.
As the new user, plb, deletion of the original user xxxxx@immuta.com has occurred.
An attempt to delete the project as the now sole owner of the project, plb, is made. The project cannot be deleted.
What is required to delete the problematic Schema Project?
This is a known behaviour and an open bug currently exists at the time of writing this knowledge base article, June 2023.
Customers will need to engage with Immuta Support as correcting the underlying problem will require their assistance.
