Hide Forgot
Description of problem: katello-service ostensibly manages all the services attached to the satellite or a capsule, however it doesn't manage smart_proxy_dynflow_core. How reproducible: katello-service <anything> doesn't list smart_proxy_dynflow_core Steps to Reproduce: 1. katello-service restart Actual results: smart_proxy_dynflow_core isn't restarted Expected results: smart_proxy_dynflow_core is restarted
Created redmine issue http://projects.theforeman.org/issues/16373 from this bug
Upstream bug assigned to stbenjam
Upstream bug component is Content Management
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16373 has been resolved.
Verified in 6.3.0 snap 10 - satellite-6.3.0-16.0.beta.el7sat.noarch When running katello-service restart, I can see smart_proxy_dynflow_core in the included services: sudo katello-service restart /usr/sbin/service-wait foreman-tasks stop Redirecting to /bin/systemctl stop foreman-tasks.service /usr/sbin/service-wait httpd stop Redirecting to /bin/systemctl stop httpd.service /usr/sbin/service-wait pulp_celerybeat stop Redirecting to /bin/systemctl stop pulp_celerybeat.service /usr/sbin/service-wait foreman-proxy stop Redirecting to /bin/systemctl stop foreman-proxy.service /usr/sbin/service-wait pulp_streamer stop Redirecting to /bin/systemctl stop pulp_streamer.service /usr/sbin/service-wait pulp_resource_manager stop Redirecting to /bin/systemctl stop pulp_resource_manager.service /usr/sbin/service-wait smart_proxy_dynflow_core stop Redirecting to /bin/systemctl stop smart_proxy_dynflow_core.service /usr/sbin/service-wait pulp_workers stop Redirecting to /bin/systemctl stop pulp_workers.service /usr/sbin/service-wait tomcat stop Redirecting to /bin/systemctl stop tomcat.service /usr/sbin/service-wait squid stop Redirecting to /bin/systemctl stop squid.service /usr/sbin/service-wait qdrouterd stop Redirecting to /bin/systemctl stop qdrouterd.service /usr/sbin/service-wait qpidd stop Redirecting to /bin/systemctl stop qpidd.service /usr/sbin/service-wait postgresql stop Redirecting to /bin/systemctl stop postgresql.service /usr/sbin/service-wait mongod stop Redirecting to /bin/systemctl stop mongod.service Success! /usr/sbin/service-wait mongod start Redirecting to /bin/systemctl start mongod.service /usr/sbin/service-wait postgresql start Redirecting to /bin/systemctl start postgresql.service /usr/sbin/service-wait qpidd start Redirecting to /bin/systemctl start qpidd.service /usr/sbin/service-wait qdrouterd start Redirecting to /bin/systemctl start qdrouterd.service /usr/sbin/service-wait squid start Redirecting to /bin/systemctl start squid.service /usr/sbin/service-wait tomcat start Redirecting to /bin/systemctl start tomcat.service /usr/sbin/service-wait pulp_workers start Redirecting to /bin/systemctl start pulp_workers.service /usr/sbin/service-wait smart_proxy_dynflow_core start Redirecting to /bin/systemctl start smart_proxy_dynflow_core.service /usr/sbin/service-wait pulp_resource_manager start Redirecting to /bin/systemctl start pulp_resource_manager.service /usr/sbin/service-wait pulp_streamer start Redirecting to /bin/systemctl start pulp_streamer.service /usr/sbin/service-wait foreman-proxy start Redirecting to /bin/systemctl start foreman-proxy.service /usr/sbin/service-wait pulp_celerybeat start Redirecting to /bin/systemctl start pulp_celerybeat.service /usr/sbin/service-wait httpd start Redirecting to /bin/systemctl start httpd.service /usr/sbin/service-wait foreman-tasks start Redirecting to /bin/systemctl start foreman-tasks.service Success!
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/RHSA-2018:0336
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/RHSA-2018:0336