Skip to main content
print this page

Users losing access to redshift tables and views after running user repair

· 2 min read
Fix Available
Fix Available
This bug has been fixed
Patch Available
Patch Available
This bug has a patch available for affected versions

Users are losing access to redshift tables and views after running user repair or by generating access parity report

Affected Versions: 2.0 1.14

Fix Version: 2.0* 2.1

2.0*

Customers upgrading to 2.0 after March 16, 2023 does not require explicit patching as the fix will be part of the release artifacts.

Root cause(s)​

In user repair and access-parity functionality, it checks and fixes the redshift permission mismatches for Datasets, Views and Domains.

In this process, It lists out domains with tenant information i.e. “TenantName” attribute where as the existing domains i.e. domains created before the multi-tenancy feature doesn't have TenantName attribute.

When user runs user repair or access-parity functionality, It is not considering these existing domains as valid domains and therefore removing the redshift permissions for them.

Same thing is getting applied to datasets without TenantName attribute and also the materialized views which are nothing but a redshift table (mv_tbl) in the backend terminology.

Impact​

After completing the user repair action, system will remove the redshift tables and views access for all the users. Users will not be able to query any data present in the redshift cluster. There is no impact to the actual data present in the cluster.

Mitigation​

Fix available

Fix is available in Amorphic version 2.1. Please upgrade to the latest version to resolve this issue.

Patch available

Patch is available for Amorphic versions v2.0.

Please contact amorphic-support@cloudwick.com to patch your application.

Timeline​

gantt
    title Timeline
    dateFormat YYYY-MM-DD
    tickInterval 7day
    axisFormat %b-%d
    todayMarker off
    section Tracker
        %% update the ticket number and date of bug report
        CLOUD-3015 : done, 2023-01-04, 0d
    section Identification
        Reported : crit, des1, 2023-01-04, 1d
    section Mitigation
        %% Update number of days took for each step below
        Root cause analysis : 2023-01-06, 1d
        Bug Fixed: crit, done, 2023-01-06, 1d
    section Delivery
        %% update the date of each step below
        testing complete: milestone, 2023-03-15, 0d
        patch avaialble: milestone, 2023-03-16, 0d
  • 2023-01-04: Bug reported/identified (CLOUD-3015)
  • 2023-01-06: Bug triaged
  • 2023-01-06: Bug fixed
  • 2023-03-15: Testing of patch on v2.0 is completed
  • 2023-03-16: Patch for v2.0 released
  • 2023-03-28: Amorphic version 2.1 Released with the bugfix