Bug 1563211

Summary: Service command operates with the local Postgres even when Satellite 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: UnspecifiedCC: apatel, bkearney, inecas, kgaikwad, mbacovsk, mmccune, sghai
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:25:51 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: 1052713    

Description Martin Bacovsky 2018-04-03 12:17:46 UTC 
Description of problem:
Service command in foreman-maintain operates only on local postgresql service. Even when Satellite is configured to use remote Mongo DB the foreman-maintain service restarts local postgres and returns its status.

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


How reproducible:


Steps to Reproduce:
1. configure Satellite with remote DB for Foreman and/or Candlepin
2. foreman-maintain service stop 
3. see the local postgresql was stopped

Actual results:
Local postgresql was stopped

Expected results:
Local postgresql keeps running if installed and not used by neither of the satellite databases.
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 Postgres 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

Another scenarios worth considering:
 - only one DB is remote
 - Foreman DB is MySQL (or sqlite)
Comment 2 Mike McCune 2018-04-03 17:08:58 UTC 
Martin,

I'm not aware of a 'foreman-maintain service' command. foreman-maintain doesn't have this sub-command.

Is this the right component?
Comment 3 Martin Bacovsky 2018-04-04 07:39:42 UTC 
Mike, 
you are right, I forgot to add that this issue is filed in advance, sorry for that. The service command [1] just landed in foreman-maintain upstream.

[1] https://github.com/theforeman/foreman_maintain/pull/151
Comment 4 Martin Bacovsky 2018-05-14 18:07:25 UTC 
Created redmine issue http://projects.theforeman.org/issues/23589 from this bug
Comment 5 Satellite Program 2018-05-17 14:19:58 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/23589 has been resolved.
Comment 6 Kavita 2018-08-16 11:47:40 UTC 
Available in foreman_maintain-0.2.6 so marking it as ON_QA.
Comment 10 Bryan Kearney 2020-03-05 16:25:51 UTC 
The current version of foreman_maintain includes this fix.
Comment 11 Bryan Kearney 2020-03-05 17:25:26 UTC 
The current version of foreman_maintain includes this fix.