Bug 1556927

Summary: service command operates with the local Mongo even when Pulp uses remote DB
Product: Red Hat Satellite Reporter: Martin Bacovsky <mbacovsk>
Component: Satellite MaintainAssignee: Anurag Patel <apatel>
Status: CLOSED CURRENTRELEASE QA Contact: Lucie Vrtelova <lvrtelov>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: apatel, bkearney, inecas, kgaikwad
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-05 16:23:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1555310    

Description Martin Bacovsky 2018-03-15 14:45:25 UTC 
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
Comment 3 Martin Bacovsky 2018-05-14 18:08:19 UTC 
Created redmine issue http://projects.theforeman.org/issues/23590 from this bug
Comment 4 Satellite Program 2018-05-17 14:04:52 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/23590 has been resolved.
Comment 5 Kavita 2018-08-16 11:49:27 UTC 
It is available in foreman_maintain-0.2.6 so marking it as ON_QA.
Comment 8 Bryan Kearney 2020-03-05 16:23:57 UTC 
The current version of foreman_maintain includes this fix.