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 2172293 - use_vmac not allowed with unicast vrrp, after keepalived update to 2.1.5-9
Summary: use_vmac not allowed with unicast vrrp, after keepalived update to 2.1.5-9
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: keepalived
Version: 8.7
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Ryan O'Hara
QA Contact: cluster-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-21 21:10 UTC by Curtis Taylor
Modified: 2024-01-21 04:25 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-22 20:07:35 UTC
Type: Bug
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-7694 0 None Migrated None 2023-09-22 20:06:13 UTC
Red Hat Issue Tracker RHELPLAN-149595 0 None None None 2023-02-21 21:11:41 UTC

Description Curtis Taylor 2023-02-21 21:10:30 UTC
Description of problem:
After update from keepalived 2.0.10 to 2.1.5-9 in RHEL8 attempt to use use_vmac reports:

    Cannot use VMAC/ipvlan with unicast peers - clearing use_vmac

This worked in Keepalived 2.0.10.

Keepalived VRRP cluster should support the use of use_vmac, vmac_xmit_base and unicast peering.

Needed commit:

https://github.com/acassen/keepalived/pull/1733/commits/97429b3b7e6ec2f5b9c93a5d507b152bab30f919

Version-Release number of selected component (if applicable):
keepalived 2.1.5-9.

How reproducible:

Steps to Reproduce:
1. 
Start keepalived to 
$ cat keepalived.conf
! Configuration File for keepalived

global_defs {
    vrrp_version 3
    enable_script_security
    script_user root
    nftables
}

vrrp_script check_peer_HE {
    script /usr/local/bin/check_peer_HE.sh
    interval 2
}

vrrp_instance VI_1 {
    interface core
    use_vmac
    vmac_xmit_base
    priority 100
    advert_int 1
    virtual_router_id 51
    virtual_ipaddress {
        10.0.0.1
    }
    unicast_src_ip 10.0.0.3
    unicast_peer {
      10.0.0.2
    }
    track_script {
	check_peer_HE
    }
    garp_master_delay 10
    garp_master_repeat 1
    garp_lower_prio_delay 10
    garp_lower_prio_repeat 1
    garp_master_refresh 60
    garp_master_refresh_repeat 2
}

Actual results:

    Cannot use VMAC/ipvlan with unicast peers - clearing use_vmac

Expected results:

Keepalived allows use_vmac with vmac_xmit_base set.

Additional info:

This is affecting a production environment, by disabling use_vmac capability and reducing high availability of a network system which contains devices that require long lived arp caches. These devices are unable to handle the failover of VRRP clusters with out the use_vmac feature.

Customer provided link to regression fix from upstream source: https://github.com/acassen/keepalived/pull/1733/commits/97429b3b7e6ec2f5b9c93a5d507b152bab30f919

Comment 6 Mithil Mhatre 2023-07-25 02:15:05 UTC
Hello Team,

Any update on this?

Comment 8 RHEL Program Management 2023-09-22 20:04:07 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 9 RHEL Program Management 2023-09-22 20:07:35 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 10 Red Hat Bugzilla 2024-01-21 04:25:35 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.