Issue Summary

      This ticket is used to track a bug on RDS - after Postgres 10 upgrade, Jira may fail to start.

      https://dba.stackexchange.com/questions/237359/aws-rds-postgresql-master-user-lost-all-privileges-after-upgrading-from-v9-6

      When ugprading to Postgres 10 on AWS RDS, Jira can't start.
      It's because after upgrade, public schema lost access privileges.

      Steps to Reproduce

      1. Connect to postgres sever (psql)
      2. connect to jira database by \c <jiradb>
      3. list out schemas \dn+

      Expected Results

      1. rdsadmin user has access privileges
                                List of schemas
        Name  |  Owner   |  Access privileges   |      Description
      --------+----------+----------------------+------------------------
       public | rdsadmin | rdsadmin=UC/rdsadmin+| standard public schema
              |          | =UC/rdsadmin         |
      (1 row)
      

      Actual Results

      1. access privileges are lost.
            List of schemas
          Name  |  Owner   | Access privileges |      Description
        --------+----------+-------------------+------------------------
         public | rdsadmin |                   | standard public schema
        (1 row)
        

      Workaround

      Grant schema access to confluence user.

      confluence=> ALTER SCHEMA public OWNER to <jira_db_user>;
      ALTER SCHEMA
      confluence=> GRANT ALL ON SCHEMA public TO <jira_db_user>;
      GRANT
      

            [JRASERVER-72246] Postgres upgrade on AWS RDS Jira can't find tables

            Artur Gniadzik made changes -
            Resolution New: Cannot Reproduce [ 5 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]
            Artur Gniadzik made changes -
            Description Original: h3. Issue Summary

            This ticket is used to track a bug on RDS - after Postgres 10 upgrade, Jira may fail to start.

            [https://dba.stackexchange.com/questions/237359/aws-rds-postgresql-master-user-lost-all-privileges-after-upgrading-from-v9-6]


             When ugprading to Postgres 10 on AWS RDS, Jira can't start.
             It's because after upgrade, public schema lost access privileges.
            h3. Steps to Reproduce
             # Connect to postgres sever (psql)
             # connect to jira database by \c <jiradb>
             # list out schemas \dn+

            h3. Expected Results
             # rdsadmin user has access privileges

            {code:java}
                                      List of schemas
              Name | Owner | Access privileges | Description
            --------+----------+----------------------+------------------------
             public | rdsadmin | rdsadmin=UC/rdsadmin+| standard public schema
                    | | =UC/rdsadmin |
            (1 row)
            {code}
            h3. Actual Results
             # access privileges are lost.
            {code:java}
                List of schemas
              Name | Owner | Access privileges | Description
            --------+----------+-------------------+------------------------
             public | rdsadmin | | standard public schema
            (1 row)
            {code}

            h3. Workaround

            Grant schema access to confluence user.
            {code:java}
            confluence=> ALTER SCHEMA public OWNER to <jira_db_user>;
            ALTER SCHEMA
            confluence=> GRANT ALL ON SCHEMA public TO <jira_db_user>;
            GRANT
            {code}
            New: h3. Issue Summary

            This ticket is used to track a bug on RDS - after Postgres 10 upgrade, Jira may fail to start.

            [https://dba.stackexchange.com/questions/237359/aws-rds-postgresql-master-user-lost-all-privileges-after-upgrading-from-v9-6]

            When ugprading to Postgres 10 on AWS RDS, Jira can't start.
             It's because after upgrade, public schema lost access privileges.
            h3. Steps to Reproduce
             # Connect to postgres sever (psql)
             # connect to jira database by \c <jiradb>
             # list out schemas \dn+

            h3. Expected Results
             # rdsadmin user has access privileges

            {code:java}
                                      List of schemas
              Name | Owner | Access privileges | Description
            --------+----------+----------------------+------------------------
             public | rdsadmin | rdsadmin=UC/rdsadmin+| standard public schema
                    | | =UC/rdsadmin |
            (1 row)
            {code}
            h3. Actual Results
             # access privileges are lost.
            {code:java}
                List of schemas
              Name | Owner | Access privileges | Description
            --------+----------+-------------------+------------------------
             public | rdsadmin | | standard public schema
            (1 row)
            {code}

            h3. Workaround

            Grant schema access to confluence user.
            {code:java}
            confluence=> ALTER SCHEMA public OWNER to <jira_db_user>;
            ALTER SCHEMA
            confluence=> GRANT ALL ON SCHEMA public TO <jira_db_user>;
            GRANT
            {code}
            SET Analytics Bot made changes -
            UIS Original: 8 New: 7
            Bugfix Automation Bot made changes -
            Support reference count Original: 2 New: 1
            Artur Gniadzik made changes -
            Remote Link Original: This issue links to "Page (Confluence)" [ 543352 ]
            SET Analytics Bot made changes -
            UIS Original: 1 New: 8
            SET Analytics Bot made changes -
            UIS New: 1
            Bugfix Automation Bot made changes -
            Support reference count Original: 1 New: 2
            Artur Gniadzik made changes -
            Status Original: Needs Triage [ 10030 ] New: Gathering Impact [ 12072 ]
            Artur Gniadzik made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 543352 ]

              Unassigned Unassigned
              emarghidan Eduard M
              Affected customers:
              0 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: