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 1860444

Summary:	After the system reboot, capsule setup(upgraded or newly installed 6.8 capsule) fails to start the tomcat service
Product:	Red Hat Satellite	Reporter:	Devendra Singh <desingh>
Component:	Installation	Assignee:	Eric Helms <ehelms>
Status:	CLOSED ERRATA	QA Contact:	Devendra Singh <desingh>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.8.0	CC:	ahumbe, aupadhye, ehelms, mmccune, vijsingh
Target Milestone:	6.8.0	Keywords:	BetaBlocker, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 13:04:32 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:

Description Devendra Singh 2020-07-24 15:17:38 UTC

Description of problem: After the system reboot, capsule upgrade setup fails to start the "foreman-proxy" service

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

How reproducible:
always (4/4)

Steps to Reproduce:
1. Upgrade Satellite from 6.7 to 6.8 
2. Reboot satellite after upgrade, all satellite services comes to upstate.
3. Upgrade Capsule from 6.7 to 6.8
4. Reboot Capsule after upgrade, foreman-proxy service failed to come up state.

I wait 3 to 4 hours but foreman-proxy not come to upstate automatically.

Actual results:
After Capsule reboot foreman-proxy service failed to come in upstate.

Expected results:
All satellite services come to upstate after reboot.

Additional info:
The services come to upstate, If trigger foreman-maintan restart again on capsule.

Comment 5 Mike McCune 2020-07-28 04:27:51 UTC

Ashish,


Tomcat is a Satellite only service, see:

https://bugzilla.redhat.com/show_bug.cgi?id=1859705#c3

Comment 8 Bryan Kearney 2020-07-28 16:06:09 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30506 has been resolved.

Comment 9 Devendra Singh 2020-08-11 10:52:03 UTC

Verified in 6.8 Snap11.

Comment 12 errata-xmlrpc 2020-10-27 13:04:32 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