Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1859705

Summary:	Tomcat is not running on fresh Capsule installation
Product:	Red Hat Satellite	Reporter:	Ondrej Gajdusek <ogajduse>
Component:	Installation	Assignee:	Eric Helms <ehelms>
Status:	CLOSED ERRATA	QA Contact:	Devendra Singh <desingh>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.8.0	CC:	ahumbe, apatel, aupadhye, ehelms, kgaikwad, mawerner, mmccune, vsedmik
Target Milestone:	6.8.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	Tomcat is not running on fresh Capsule installation	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 13:04:20 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1818012

Description Ondrej Gajdusek 2020-07-22 18:05:52 UTC

Description of problem:
`foreman-maintain service status` fails on fresh Capsule installation. foreman-maintain is checking also for candlepin service. tomcat.service is not running on the system with fresh Capsule installation.

$ foreman-maintain service status 
Running Status Services
================================================================================
Get status of applicable services: 

Displaying the following service(s):
rh-mongodb34-mongod, qdrouterd, qpidd, squid, pulp_celerybeat, pulp_resource_manager, pulp_streamer, pulp_workers, smart_proxy_dynflow_core, tomcat, httpd, puppetserver, foreman-proxy

... output omitted ...

| displaying tomcat                                                             
● tomcat.service - Apache Tomcat Web Application Container
   Loaded: loaded (/usr/lib/systemd/system/tomcat.service; disabled; vendor preset: disabled)
   Active: inactive (dead)

... output omitted ...

/ All services displayed                                              [FAIL]    
Some services are not running (tomcat)
--------------------------------------------------------------------------------
Scenario [Status Services] failed.
... output omitted ...

Version-Release number of selected component (if applicable):
candlepin-3.1.14-1.el7sat.noarch
satellite-capsule-6.8.0-0.7.beta.el7sat.noarch
satellite-maintain-0.0.1-1.el7sat.noarch
rubygem-foreman_maintain-0.6.8-1.el7sat.noarch

How reproducible:
always

Steps to Reproduce:
1. foreman-maintain service status

Actual results:
foreman-maintain fails during the services check, tomcat is not running

Expected results:
All services that foreman-maintain is checking for should be running on clean Capsule installation.

Comment 3 Mike McCune 2020-07-28 04:27:10 UTC

There should be no Tomcat on Capsules, it should not be installed or enabled and foreman-maintain needs to *not* check or manage this service on Capsules.  

Tomcat is a Satellite only service.

Comment 4 Kavita 2020-07-28 13:43:10 UTC

From Mike's comment 3, correcting the component back to foreman-maintain.

Comment 7 Devendra Singh 2020-08-31 17:59:21 UTC

Verified on 6.8.0 Snap13.

Comment 10 errata-xmlrpc 2020-10-27 13:04:20 UTC

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 (Important: Satellite 6.8 release), 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-2020:4366