Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong schema used in postgres #102

Open
bronweg opened this issue Nov 14, 2018 · 2 comments
Open

Wrong schema used in postgres #102

bronweg opened this issue Nov 14, 2018 · 2 comments
Labels

Comments

@bronweg
Copy link

bronweg commented Nov 14, 2018

When PostgreSQL DB chosen, public schema is used instead of ambari schema.
This is not a problem until you want to upgrade the cluster.

When I tried to upgrade my cluster (installed with that ansible playbook), I fault on ambari schema doesn't exist. To avoid this, I ran ambari-server setup with --postgresschema=public, and manually changed that schema owner to ambari user. Only after that I successfully upgraded my cluster.

According to that documents: 2.6, 2.7, ambari schema should be created during the installation and ambari user should be the owner of that schema, but that doesn't happen here.

@alexandruanghel
Copy link
Contributor

Wow, great find @bronweg this is definitely a bug in the playbooks.

I'll work on a fix, thanks!

@lhoss
Copy link
Contributor

lhoss commented Feb 27, 2019

When I tried to upgrade my cluster (installed with that ansible playbook), I fault on ambari schema doesn't exist.

👍 I had ran into exact same issue
and I agree it would be nice to fix this the role (if I had some spare time!)

I ran ambari-server setup with --postgresschema=public

Your fix (1.step) was even more elegant. My fix was to change the related schema parameter in /etc/ambari-server/conf/ambari.properties

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants