Red Hat Bugzilla – Bug 1539105
Missing script which would restart all the rhui related services on RHUA and CDS [regression]
Last modified: 2018-09-05 13:04:51 EDT
Description of problem: In RHUI2, there were init scripts to restart all the relevant services: RHUA: service pulp-server restart CDS: pulp-cds restart Missing them in RHUI3. Version-Release number of selected component (if applicable): RHUI 3.0 How reproducible: 100% Actual results: No easy way to restart services like we were used to do in RHUI 2. Expected results: It should be possible to restart services with the script like in RHUI 2.
Hello Michal, Since pulp X.Y. there is no such service as pulp-server. I'm sorry I don't remember those X.Y. exactly, I think it was 1 something. RHUI3 uses pulp 2.8. Therefore to restart pulp services on RHUA run: $ for s in {pulp_workers,pulp_resource_manager,pulp_celerybeat,httpd,goferd}; do sudo systemctl stop $s; done; or simply $ systemctl restart pulp* It's not RHUI, it' pulp. I recommend to close this issue, if there is no any objections.
s/stop/restart
(In reply to Irina Gulina from comment #3) > Hello Michal, > > Since pulp X.Y. there is no such service as pulp-server. I'm sorry I don't > remember those X.Y. exactly, I think it was 1 something. RHUI3 uses pulp 2.8. > > Therefore to restart pulp services on RHUA run: > $ for s in > {pulp_workers,pulp_resource_manager,pulp_celerybeat,httpd,goferd}; do sudo > systemctl stop $s; done; > > or simply > > $ systemctl restart pulp* > > It's not RHUI, it' pulp. I recommend to close this issue, if there is no any > objections. Hello Irina, Would be nice to have it, since RHUI 2 had it before (regardless if it was pulp or rhui feature, it doesn't really matter from end user perspective) and Satellite 5 and Satellite 6 which are also System Management products do have a script which restarts all the services related to the product.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2649