Are there any customers directly impacted by this bug? Which ones?
No
Bug Category
[ ] Connection Manager
[ ] Connection Test
[ ] Creating Pipeline
[ ] Executing Pipeline
[ ] Cataloging Data Asset
[x ] Other
Describe the bug
While trying to delete a customer, the terraform applyfails because it can't delete the roles on postgresql from nimbus and metabase because some objects depends on the role.
However, when listing the objects that depend on the role using the following query some time after running the terraform:
SELECT
n.nspname as schema_name,
c.relname as object_name,
CASE c.relkind
WHEN 'r' THEN 'table'
WHEN 'v' THEN 'view'
WHEN 'i' THEN 'index'
WHEN 'S' THEN 'sequence'
WHEN 's' THEN 'special'
WHEN 'f' THEN 'foreign table'
END as object_type
FROM pg_depend d
JOIN pg_class c ON d.objid = c.oid
JOIN pg_namespace n ON c.relnamespace = n.oid
WHERE d.refobjid = 'nimbus-cashu'::regrole;
No dependent objects are found. So, I was able to drop the role using the following command:
drop role "nimbus-basealpha";
To fix this permanently, we will probably have to fix our customer module to only delete the role on postgresql to only delete the role when every other dependent object had been deleted.
Workaround:
Drop the role using the root user
or
Run the terraform again some time after the first running.
When the bug happened:
2022-03-09: While trying to delete the customers: basealpha,cashu and duxnutritioncom
Mandatory informations:
Are there any customers directly impacted by this bug? Which ones?
No
Bug Category
Describe the bug
While trying to delete a customer, the![image](https://user-images.githubusercontent.com/40280691/224185400-34a3bacc-3e32-4c27-b08a-c3c9a2c20719.png)
terraform apply
fails because it can't delete the roles on postgresql from nimbus and metabase because some objects depends on the role.However, when listing the objects that depend on the role using the following query some time after running the terraform:
No dependent objects are found. So, I was able to drop the role using the following command:
To fix this permanently, we will probably have to fix our customer module to only delete the role on postgresql to only delete the role when every other dependent object had been deleted.
Workaround:
or
When the bug happened:
basealpha
,cashu
andduxnutritioncom