Do we want katello-service to restart capsule services automatically in case capsule is installed on same system as Satellite 6 server?

Created redmine issue http://projects.theforeman.org/issues/6781 from this bug

*** Bug 1120845 has been marked as a duplicate of this bug. ***

We had a couple of conversations upstream on the mailing list, and I'm not really sure I see the value of this.

A Capsule can manage a dozen different services, many of which may be external to the capsule.  Also, all of the services are not really related, so I can't really ever see a case that some change is going to need you to restart, say, DHCP and Pulp at the same time - it's far too big a hammer.  

Restart foreman-proxy, or the particular service you're working on (e.g. named).

The main issue it seems is just pulp, so perhaps a bug should go to pulp to provide a tool to restart all the content-related services in the right order.

(In reply to Stephen Benjamin from comment #6)
> We had a couple of conversations upstream on the mailing list, and I'm not
> really sure I see the value of this.
> 
The gap is there's no equivalent of katello-service for Capsule (whereas Satellite 6, Satellite 5, and Satellite Proxy 5 all have a single command to restart Satellite or Proxy services).

One use case for example is when applying errata to a Capsule server and needing to restart services.  Mike just wrote https://access.redhat.com/solutions/1276863 "How do I apply errata updates to my Satellite 6 Server or Capsule?" which will be referenced by all Satellite 6/Capsule errata going forward as part of the instructions, and this references the attached https://access.redhat.com/solutions/1187883 for steps (thanks Justin) how to stop/start Capsule services.  What's missing still though is the actual utility to do this.

> A Capsule can manage a dozen different services, many of which may be
> external to the capsule.  Also, all of the services are not really related,
> so I can't really ever see a case that some change is going to need you to
> restart, say, DHCP and Pulp at the same time - it's far too big a hammer.  
> 
> Restart foreman-proxy, or the particular service you're working on (e.g.
> named).
> 
> The main issue it seems is just pulp, so perhaps a bug should go to pulp to
> provide a tool to restart all the content-related services in the right
> order.
Is there a way to automatically detect if these services are being used, or provide user an option whether to include these services (named/dhcp) in stop/start?  Failing that, we could print out a message for the user either to manually restart those, or restart them and let the user be aware.

Thanks,
Xixi

including a snapshot of https://access.redhat.com/solutions/1187883 for reference:

"
Resolution

In some instances it is necessary to manually stop and then restart the Capsule services.
One method is to reboot the Capsule
You may also individually stop, start, or restart the services using;

service <service name> stop | start | restart

    The affected services include;
        dhcpd
        dns
        httpd
        pulp_celerybeat
        pulp_workers
        pulp_resource_manager
        foreman_proxy

To restart the pulp, foreman-proxy, and puppet master portions:

for i in pulp_celerybeat pulp_resource_manager pulp_workers httpd foreman-proxy; do service $i stop; done
for i in pulp_celerybeat pulp_resource_manager pulp_workers httpd foreman-proxy; do service $i start; done

if using the dns feature or dhcp feature, simply restart their respective services:

service named restart
service dhcpd restart

"

Upstream bug assigned to stbenjam

The foreman service should be "foreman-proxy" and *not* "foreman_proxy"  Note: dash instead of underscore.

Moving to POST since upstream bug http://projects.theforeman.org/issues/6781 has been closed
-------------
Anonymous
Applied in changeset commit:katello|3e035bf0e6d7623a825bbdf586f330f5021c8e3f.

ALSO pull in https://github.com/Katello/katello-installer/pull/217

hi 

please provide verification steps

thanks

This is currently blocked, but steps would be:

1. Run `katello-service status` on a capsule

2. You'll get the status of all the services, it will look something like this, but depends on the features you've enabled and the OS:


mongod (pid  23580) is running...
listening on 127.0.0.1:27017
connection test successful
celery init v10.0.
Using config script: /etc/default/pulp_resource_manager
node resource_manager (pid 23799) is running...
celery init v10.0.
Using config script: /etc/default/pulp_workers
node reserved_resource_worker-0 (pid 23993) is running...
node reserved_resource_worker-1 (pid 24018) is running...
node reserved_resource_worker-2 (pid 24047) is running...
node reserved_resource_worker-3 (pid 24074) is running...
node reserved_resource_worker-4 (pid 24105) is running...
node reserved_resource_worker-5 (pid 24134) is running...
node reserved_resource_worker-6 (pid 24163) is running...
node reserved_resource_worker-7 (pid 24192) is running...
celery init v10.0.
Using configuration: /etc/default/pulp_workers, /etc/default/pulp_celerybeat
pulp_celerybeat (pid 24248) is running.
httpd (pid  24288) is running...

moving to modified to reflect the dependency on https://bugzilla.redhat.com/show_bug.cgi?id=1220309

hi

here this bz is dependent on 
https://bugzilla.redhat.com/show_bug.cgi?id=1220309
hence once this is verified can proceed further
thanks

hi

here this bz is dependent on 
https://bugzilla.redhat.com/show_bug.cgi?id=1228195
hence once this is verified can proceed further
thanks

Removing dependency on bug 1228195 as I am not sure it is a legit bug.  I installed compose from latest capsule just fine

taking this bz.  Verified in snap 8

This bug is slated to be released with Satellite 6.1.

This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.