Bug #23590: service command operates with the local Mongo even when Pulp uses remote DB - Foreman Maintain - Foreman

Actions

Copy link

Bug #23590

closed

service command operates with the local Mongo even when Pulp uses remote DB

Added by Martin Bacovsky about 6 years ago. Updated about 6 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Anurag Patel

Category:

Target version:

Difficulty:

Triaged:

Bugzilla link:

1556927

Pull request:

https://github.com/theforeman/foreman_maintain/pull/178

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

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

Description of problem:
Service command in foreman-maintain operates only on local mongod service. Even when Satellite is configured to use remote Mongo DB the foreman-maintain service restarts local mongod and return sits status.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. configure Satellite with remote Mongo DB
2. foreman-maintain service stop
3. see the local mongod was stopped

Actual results:
Local mongod was stoped

Expected results:
Local mongod keeps running.
Maybe warning that the DB is remote and can not be stopped

Additional info:

foreman-maintain service status should return some status of the remote Mongo DB (if we can connect with our current setup, if the serice is up, that it is remote and can not be stopped, maybe ping latency and ssl presence on the connection)

foreman-maintain start should check if the remote DB is up and accessible