This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 2127398 - backport commit "Allow persistence_granularity to be 0.0.0.0" for keepalived version 1.3.5, RHEL 7
Summary: backport commit "Allow persistence_granularity to be 0.0.0.0" for keepalive...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: keepalived
Version: 7.9
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Ryan O'Hara
QA Contact: cluster-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-16 07:55 UTC by suresh kumar
Modified: 2024-01-21 04:25 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-22 19:57:38 UTC
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-7678 0 None Migrated None 2023-09-22 19:57:28 UTC
Red Hat Issue Tracker RHELPLAN-134147 0 None None None 2022-09-16 08:03:43 UTC

Description suresh kumar 2022-09-16 07:55:14 UTC 
Description of problem:
SIP request message with same call-id, but different source IP is routed to different server as if it was newly initiated call-id and connection breaks.

Setup:
=======

SIP clients ------------> keepalived Server ------> Real Server
                           192.168.100.116          192.168.100.118
                                                    192.168.100.121



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

How reproducible:
Always by customer


Actual results:
Current Flow:
SIPP(192.168.100.171) --- INVITE ---> LB(192.168.100.116) ---> RealServer(192.168.100.118)
SIPP(192.168.100.171) <----- 200 ----- RealServer(192.168.100.118)
SIPP(192.168.100.170) ----- ACK -----> LB(192.168.100.116) ---> RealServer(192.168.100.121)
SIPP(192.168.100.170) ----- BYE -----> LB(192.168.100.116) ---> RealServer(192.168.100.121)

# ipvsadm -Ln --connection --persistent-conn
IPVS connection entries
pro expire state       source             virtual            destination        pe name          pe_data
UDP 14:07  UDP         192.168.100.170:0  192.168.100.116:5060 192.168.100.121:5060 sip                1-16760.100.171
UDP 14:07  UDP         192.168.100.171:0  192.168.100.116:5060 192.168.100.118:5060 sip                1-16760.100.171

The call-id is same, but packet from 192.168.100.171 is routed to 192.168.100.118



Expected results:
==================

SIPP(192.168.100.171) --- INVITE ---> LB(192.168.100.116) ---> RealServer(192.168.100.118)
SIPP(192.168.100.171) <----- 200 ----- RealServer(192.168.100.118)
SIPP(192.168.100.170) ----- ACK -----> LB(192.168.100.116) ---> RealServer(192.168.100.118) ***
SIPP(192.168.100.170) ----- BYE -----> LB(192.168.100.116) ---> RealServer(192.168.100.118) ***

Additional info:
==================
keepalived configuration used:

virtual_server 192.168.100.116 5060 {
# virtual_server fd00::7ea1:10:1:1:145 5060 {
    delay_loop 5
    lb_algo rr
    lb_kind DR
    ops 
    persistence_timeout 60
    persistence_granularity 0.0.0.0  <----------------- This is not working
    persistence_engine sip 
    protocol UDP
Comment 6 Mithil Mhatre 2023-08-09 08:05:43 UTC 
Hello Team,

Any update on this?


Thanks,
Mithil
Comment 9 RHEL Program Management 2023-09-22 19:49:06 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 10 RHEL Program Management 2023-09-22 19:57:38 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Comment 11 Red Hat Bugzilla 2024-01-21 04:25:28 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.