Skip to content

Conversation

@wbclark
Copy link
Collaborator

@wbclark wbclark commented Feb 11, 2020

No description provided.

@wbclark wbclark force-pushed the postgres_user branch 2 times, most recently from e6fc2da to fb47a46 Compare February 11, 2020 21:47
@wbclark
Copy link
Collaborator Author

wbclark commented Feb 11, 2020

@ekohl this fails in spec/acceptance/basic_spec.rb when I change the postgresql_database_user to a value other than 'pulp'. For example with the user 'pulpcore' we get a password authentication error for that user during django-admin migrate --noinput. Any idea why that happens?

@ekohl
Copy link
Member

ekohl commented Feb 11, 2020

On the same host it may be using ident auth rather than password auth which would fail. Not entirely sure.

@ehelms ehelms merged commit d469252 into theforeman:master Feb 11, 2020
@evgeni
Copy link
Member

evgeni commented Jan 28, 2025

@ekohl this fails in spec/acceptance/basic_spec.rb when I change the postgresql_database_user to a value other than 'pulp'. For example with the user 'pulpcore' we get a password authentication error for that user during django-admin migrate --noinput. Any idea why that happens?

You did not pass the username to the password hash function, so it was always computing the hash like the user is pulp ;)

#373

@wbclark
Copy link
Collaborator Author

wbclark commented Jan 28, 2025

You did not pass the username to the password hash function, so it was always computing the hash like the user is pulp ;)

Well, that would explain it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants