Bug 962700 - Katello is not restarted on template changes
Summary: Katello is not restarted on template changes
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: Nightly
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Ivan Necas
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-14 09:40 UTC by Marek Hulan
Modified: 2019-09-26 13:40 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-23 17:56:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Marek Hulan 2013-05-14 09:40:47 UTC
Description of problem:

katello-configure can change configuration files (e.g. /etc/ldap_fluff.yml) which should restart katello service, however it only reloads Apache which is in this case useless

Version-Release number of selected component (if applicable):

nightly but probably many olders

How reproducible:

always

Steps to Reproduce:
1. katello-configure katello-configure --auth-method=ldap --ldap-server=192.168.25.1
2. katello-configure katello-configure --auth-method=ldap --ldap-server=192.168.25.2
  
Actual results:

katello still uses LDAP on 192.168.25.1

Expected results:

katello reloads fresh configuration from changed config file

Additional info:

This is probaly not limited to LDAP configuration. We shoiuld go through all katello configuration files.

Comment 2 Marek Hulan 2013-06-13 06:56:04 UTC
Also when a new certificate is generated, Apache, Katello and Signo should be restarted (currently are not)

Comment 3 Mike McCune 2014-06-06 03:33:05 UTC
now in katello-installer but the above still stands.  Any run should restart services if changes were made.

Comment 4 Stephen Benjamin 2016-08-23 17:56:34 UTC
Closing this as CURRENTRELEASE as in almost every case now, the puppet-based installer notifies the correct service entries when a related file is changed.  

If there is any specific case found where that's not the case, we need a specific BZ, but I can't think of any at the moment.


Note You need to log in before you can comment on or make changes to this bug.