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 1518848 - tomcat doesn't update certificate after katello-change-hostname
Summary: tomcat doesn't update certificate after katello-change-hostname
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Backup & Restore
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: John Mitsch
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: GSS_Sat6Beta_Tracker, GSS_Sat6_Tracker 1533259
TreeView+ depends on / blocked
 
Reported: 2017-11-29 16:14 UTC by Tomer Brisker
Modified: 2021-06-10 13:45 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
The command katello-change-hostname creates an error condition when run on Satellite 6.2 during migration and upgrade. This occurs because of a bug in the version of the katello-change-hostname command in the 6.2 release. To avoid this problem, complete the upgrade to Satellite 6.3 before running the katello-change-hostname command.
Clone Of:
Environment:
Last Closed: 2018-11-26 19:32:40 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Tomer Brisker 2017-11-29 16:14:10 UTC 
Description of problem:
Tomcat doesn't change the change the server certificate to the new hostname after katello-change-hostname is run on a cloned 6.2 Satellite, leading to failure during 6.3 upgrade proccess. 

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


How reproducible:


Steps to Reproduce:
1. Clone a 6.2 Satellite
2. run `katello-change-hostname new.example.com`
3. try to upgrade satellite to 6.3 using foreman-maintain.

Actual results:
Upgrade fails in stage `foreman-rake katello:clean_backend_objects` because katello refuses to connect to candlepin due to the fact candlepin provides an invalid server certificate. 


Expected results:
Upgrade successful.

Additional info:
If upgrade failed, remove /etc/tomcat/keystore and /etc/pki/katello/keystore and rerun satellite-installer with no arguments to regenerate the correct keystores before rerunning the upgrade process.
This may have to do with the fact that katello-change-hostname was run with satellite 6.2 so that its code and puppet-cert code is an older version than that shipped in 6.3.
Comment 1 Mike McCune 2017-11-30 17:45:20 UTC 
This needs to go into 6.2.z as the katello-change-hostname is taking place on the prior version. 

It works fine in 6.3.
Comment 3 Mike McCune 2017-11-30 17:47:17 UTC 
*** WORKAROUND ***

1) remove /etc/tomcat/keystore and /etc/pki/katello/keystore 

2) rerun satellite-installer with no arguments
Comment 9 Bryan Kearney 2018-11-26 19:32:40 UTC 
Satellite 6.2 has reached maintenance support phase 2 [1]. This bug does not quality for inclusion in a 6.2.z release during this support phase. I am therefore closing this bug out.

[1] https://access.redhat.com/support/policy/updates/satellite
Note You need to log in before you can comment on or make changes to this bug.