Project

General

Profile

Actions

Bug #24789

closed

All services handled by katello-service are not handled by foreman-maintain on capsule

Added by Martin Bacovsky over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1624717

Description of problem:

On 6.4 capsule using katello-service,

  1. katello-service start

systemctl start rh-mongodb34-mongod.service

systemctl start qpidd.service

systemctl start qdrouterd.service

systemctl start squid.service

systemctl start pulp_workers.service

systemctl start pulp_celerybeat.service

systemctl start smart_proxy_dynflow_core.service

systemctl start pulp_streamer.service

systemctl start foreman-proxy.service

systemctl start pulp_resource_manager.service

systemctl start httpd.service

systemctl start puppetserver.service

systemctl start goferd.service

On 6.4 capsule using foreman-maintain service,

  1. foreman-maintain service start
    Running Start Services ================================================================================
    Check if command is run as root user: [OK]
    --------------------------------------------------------------------------------
    Start applicable services:
    Starting the following service(s):

rh-mongodb34-mongod, squid, foreman-proxy, smart_proxy_dynflow_core, pulp_streamer, pulp_celerybeat, pulp_resource_manager, pulp_workers, puppetserver

\ All services started [OK]
--------------------------------------------------------------------------------

Version-Release number of selected component (if applicable):
  1. rpm -qa | grep maintain
    rubygem-foreman_maintain-0.2.6-1.el7sat.noarch

How reproducible: always

Steps to Reproduce:
1. katello-service start
2. foreman-maintain service start

Actual results:

Diff of following service which are handled by katello-service but not foreman-maintain service.

- qpidd.service
- qdrouterd.service
- httpd.service
- goferd.service

Expected results: foreman-maintain service should able to handle those services.

Additional info:
  1. foreman-maintain service stop --only httpd
    Running Stop Services ================================================================================
    Check if command is run as root user: [OK]
    --------------------------------------------------------------------------------
    Stop applicable services:
    Stopping the following service(s):
    [FAIL]
    No services found matching your parameters
    --------------------------------------------------------------------------------
    Scenario [Stop Services] failed.

The following steps ended up in failing state:

[service-stop]

Resolve the failed steps and rerun
the command. In case the failures are false positives,
use --whitelist="service-stop"

  1. katello-service stop --only httpd
    systemctl stop httpd.service

Success!

Actions #1

Updated by The Foreman Bot over 5 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman_maintain/pull/208 added
Actions #2

Updated by Martin Bacovsky over 5 years ago

  • Status changed from Ready For Testing to Closed
Actions #3

Updated by Ivan Necas over 5 years ago

  • Fixed in Releases foreman_maintain-0.2.9 added
Actions

Also available in: Atom PDF