Project

General

Profile

Actions
Copy link

Bug #36152

closed

"Restoring postgresql global objects" step is buggy and not required

Added by Evgeni Golov about 2 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
High
Assignee:
Evgeni Golov
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
2172540
Pull request:
https://github.com/theforeman/foreman_maintain/pull/691
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=2172540

Description of problem:

The "Restoring postgresql global objects" step in "foreman-maintain restore" is buggy:
- it's executing the restore as the "foreman" user who has not the sufficient permissions to perform the actions (modifying global objects requires superuser permission)
- it sometimes fails with 'password authentication failed for user "foreman"' as the password of the user is changed during the overall restore procedure

However, it's also not required, as the only thing it's supposed to do is to (re-)create the users in the database, but that's already handled by the Installer run that happens before the Globals Restore.

To avoid any further issues, we can drop this step completely and rely on the Installer for the management of the database users.

Actions
Copy link
 #1

Updated by The Foreman Bot about 2 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Evgeni Golov
  • Pull request https://github.com/theforeman/foreman_maintain/pull/691 added
Actions
Copy link
 #2

Updated by Evgeni Golov about 2 years ago

  • Status changed from Ready For Testing to Closed
Actions
Copy link

Also available in: Atom PDF