-
Bug
-
Resolution: Cannot Reproduce
-
Medium
-
None
-
8.5.0, 8.13.0
-
8.05
-
1
-
Severity 2 - Major
-
7
-
Issue Summary
This ticket is used to track a bug on RDS - after Postgres 10 upgrade, Jira may fail to start.
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
- Connect to postgres sever (psql)
- connect to jira database by \c <jiradb>
- list out schemas \dn+
Expected Results
- 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
- 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
- is cloned from
-
CONFSERVER-59243 Upgrade to Postgres 10 on AWS RDS Confluence can't find tables
- Long Term Backlog