Bug #23673
closedrestore on external database
Description
in the lastest changes
https://github.com/theforeman/foreman_maintain/pull/169/commits/ba1c920e9019f3c712b6fea094927ad2759c4c72
in restore PR https://github.com/theforeman/foreman_maintain/pull/169
reappeared the problem with remote database
- Dropping databases - Dropping databases [FAIL] No services found matching your parameters -------------------------------------------------------------------------------- Scenario [Restore backup] failed. The following steps ended up in failing state: [restore-drop-databases] Resolve the failed steps and rerun the command. In case the failures are false positives, use --whitelist="restore-drop-databases"
feature(:service).handle_services(spinner, 'start', :only => ['postgresql'])
fails because of empty service list - postgresql is not installed so it is removed from the list
we may consider removing the whole DropDatabases step
pg_restore is used with --clean flag anyway
https://github.com/theforeman/foreman_maintain/blob/master/lib/foreman_maintain/concerns/base_database.rb#L63
so I believe it is not necessary to clean database before restore
Updated by Martin Bacovsky almost 6 years ago
- Category set to Procedure
- Status changed from New to Assigned
- Assignee set to Martin Bacovsky
- Triaged set to No
- Team Backlog Ivan added
Updated by Martin Bacovsky almost 6 years ago
- Team Backlog Foreman Maintain added
- Team Backlog deleted (
Ivan)
All the services subcommands are affected when using remote DB's and the service is not present (though unused on the server). Will fix this at first.
We may revisit restore later with moving --reset feature to f-m.
Updated by The Foreman Bot almost 6 years ago
- Pull request https://github.com/theforeman/foreman_maintain/pull/200 added
Updated by Martin Bacovsky almost 6 years ago
- Status changed from Assigned to Closed
- % Done changed from 0 to 100
Applied in changeset foreman_maintain|6a10e56f219ab9863f84a8f01271db53052ca9a9.