Bug 1838923 - Foreman-maintain takes 3 to 5 minutes to restart the services on the IPv6 machine.
Summary: Foreman-maintain takes 3 to 5 minutes to restart the services on the IPv6 mac...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Puppet
Version: 6.8.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: 6.8.0
Assignee: satellite6-bugs
QA Contact: Vladimír Sedmík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-22 04:48 UTC by Devendra Singh
Modified: 2020-07-19 09:06 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1849048 (view as bug list)
Environment:
Last Closed: 2020-07-19 09:06:48 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Devendra Singh 2020-05-22 04:48:43 UTC
Description of problem: Foreman-maintain takes 3 to 5 minutes to restart the services on the IPv6 machine. 


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

How reproducible:
always

Steps to Reproduce:
1. Install satellite 6.8 over IPv6 network
2. Restart the foreman-maintain services
3. Service restart takes 3 to 5 minutes, 

Actual results:
Foreman-maintain services restart took 3 to 5 minutes.

Expected results:
Foreman-maintain services restart should take 1 to 2 minutes.

Additional info:
Over IPv4 environment(Same version of the satellite), foreman-maintain services took 1 minute to restart the services.

Comment 7 Rehana 2020-06-16 13:39:02 UTC
Hi Devendra , 

Thank you for opening the bug. Can you please share the candlepin.log in order to enable our team troubleshoot the issue better ? 

thanks,
Rehana

Comment 8 Devendra Singh 2020-06-16 15:22:56 UTC
(In reply to Rehana from comment #7)
> Hi Devendra , 
> 
> Thank you for opening the bug. Can you please share the candlepin.log in
> order to enable our team troubleshoot the issue better ? 
> 
> thanks,
> Rehana

foreman-debug log attached in the attachment, I think it contains candlepin log.
If you need other than foreman-debug log, please let me know.

Comment 9 Barnaby Court 2020-06-17 12:44:39 UTC
Looking in the candlepin log I see: 
2020-05-22 01:00:16,897 [thread=Thread-1 (ActiveMQ-scheduled-threads)] [=, org=, csid=] ERROR org.apache.activemq.artemis.core.server - AMQ224088: Timeout (10 seconds) while handshaking with /127.0.0.1:58290 has occurred.
2020-05-22 01:00:32,063 [thread=Thread-4 (ActiveMQ-scheduled-threads)] [=, org=, csid=] ERROR org.apache.activemq.artemis.core.server - AMQ224088: Timeout (10 seconds) while handshaking with /127.0.0.1:58308 has occurred.
2020-05-22 01:00:48,138 [thread=Thread-4 (ActiveMQ-scheduled-threads)] [=, org=, csid=] ERROR org.apache.activemq.artemis.core.server - AMQ224088: Timeout (10 seconds) while handshaking with /127.0.0.1:58312 has occurred.

Seeing the attempt to bind to 127.0.0.1, was the broker.xml & the candlepin config updated to use an ipv6 based address?


Note You need to log in before you can comment on or make changes to this bug.