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)
Martin, I'm not aware of a 'foreman-maintain service' command. foreman-maintain doesn't have this sub-command. Is this the right component?
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
Created redmine issue http://projects.theforeman.org/issues/23589 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/23589 has been resolved.
Available in foreman_maintain-0.2.6 so marking it as ON_QA.
The current version of foreman_maintain includes this fix.