Bug #35831: foreman-maintain doesn't detect Apache feature on Debian due to different package/service name - Foreman Maintain - Foreman

Actions

Copy link

Bug #35831

closed

foreman-maintain doesn't detect Apache feature on Debian due to different package/service name

Added by Evgeni Golov over 1 year ago. Updated over 1 year ago.

Status:

Closed

Priority:

Normal

Assignee:

Evgeni Golov

Category:

Target version:

Difficulty:

Triaged:

Bugzilla link:

Pull request:

https://github.com/theforeman/foreman_maintain/pull/664

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

# foreman-maintain service list
Running Service List
================================================================================
List applicable services: 
dynflow-sidekiq@.service               indirect        enabled
foreman-proxy.service                  enabled         enabled
foreman.service                        enabled         enabled
postgresql.service                     enabled         enabled
puppetserver.service                   enabled         enabled

All services listed                                                   [OK]
--------------------------------------------------------------------------------

Actions

Copy link

Updated by The Foreman Bot over 1 year ago

Status changed from New to Ready For Testing
Pull request https://github.com/theforeman/foreman_maintain/pull/664 added

Actions

Copy link

Updated by Evgeni Golov over 1 year ago

Assignee deleted (~~Evgeni Golov~~)

FTR, this also affects backups -- they don't contain any Apache bits w/o the patch.

Actions

Copy link

Updated by Evgeni Golov over 1 year ago

Assignee set to Evgeni Golov

Actions

Copy link

Updated by Evgeni Golov over 1 year ago

Subject changed from foreman-maintain service list doesn't list Apache on Debian to foreman-maintain doesn't detect Apache feature on Debian due to different package/service name

Actions

Copy link