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 1901983 - candepin_events not running after changing satellite hostname
Summary: candepin_events not running after changing satellite hostname
Keywords:
Status: CLOSED DUPLICATE of bug 1897360
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: satellite-change-hostname
Version: 6.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.9.0
Assignee: satellite6-bugs
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-26 14:32 UTC by Peter Ondrejka
Modified: 2020-12-10 23:32 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-10 23:32:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Peter Ondrejka 2020-11-26 14:32:19 UTC 
Description of problem:

candepin_events not running after changing satellite hostname

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

satellite 6.9 snap 3

How reproducible:
always 

Steps to Reproduce:
1. satellite-change-hostname <new-name> -u <name> -p  <pass>
2. wait until complete, then:

hammer ping

database:         
    Status:          ok
    Server Response: Duration: 0ms
candlepin:        
    Status:          ok
    Server Response: Duration: 67ms
candlepin_events: 
    Status:          FAIL
    message:         Not running
    Server Response: Duration: 1ms
candlepin_auth:   
    Status:          ok
    Server Response: Duration: 75ms
katello_events:   
    Status:          ok
    message:         0 Processed, 0 Failed
    Server Response: Duration: 0ms
pulp:             
    Status:          ok
    Server Response: Duration: 113ms
pulp_auth:        
    Status:          ok
    Server Response: Duration: 46ms
foreman_tasks:    
    Status:          ok
    Server Response: Duration: 3ms


only thing candepin_events related in candlepin logs:

/var/log/candlepin/error.log:2020-11-26 12:11:38,003 [thread=localhost-startStop-1] [=, org=, csid=] WARN  org.apache.activemq.artemis.core.server - AMQ222165: No Dead Letter Address configured for queue katello_candlepin_event_monitor.candlepin_events in AddressSettings
/var/log/candlepin/error.log:2020-11-26 12:11:38,004 [thread=localhost-startStop-1] [=, org=, csid=] WARN  org.apache.activemq.artemis.core.server - AMQ222166: No Expiry Address configured for queue katello_candlepin_event_monitor.candlepin_events in AddressSettings


Additional info:

Running "satellite-maintain service restart" doesn't have any impact on the issue
Comment 1 Mirek Długosz 2020-11-26 15:54:59 UTC 
Peter,

I believe this is regression (i.e. candlepin was fine after hostname change in Sat 6.8), and our automation caught it. Added keywords to communicate that. Feel free to remove them if that's wrong.
Comment 6 Jonathon Turel 2020-12-10 23:32:27 UTC 

*** This bug has been marked as a duplicate of bug 1897360 ***
Note You need to log in before you can comment on or make changes to this bug.