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 1829448 - Regression related to support for multiple IPv6 addresses
Summary: Regression related to support for multiple IPv6 addresses
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: dnsmasq
Version: 8.2
Hardware: Unspecified
OS: Unspecified
urgent
medium
Target Milestone: rc
: 8.2
Assignee: Petr Menšík
QA Contact: Petr Sklenar
URL:
Whiteboard:
Depends On:
Blocks: 1829201 1834454 1836825
TreeView+ depends on / blocked
 
Reported: 2020-04-29 14:42 UTC by Slawek Kaplonski
Modified: 2020-11-04 02:52 UTC (History)
7 users (show)

Fixed In Version: dnsmasq-2.79-13.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1834454 1836825 (view as bug list)
Environment:
Last Closed: 2020-11-04 02:51:58 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Use only matching address family context (2.09 KB, patch)
2020-05-11 11:21 UTC, Petr Menšík 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:4673 0 None None None 2020-11-04 02:52:10 UTC

Description Slawek Kaplonski 2020-04-29 14:42:32 UTC 
According to Harald's email to dnsmasq ML http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2020q2/014038.html there is regression in latest dnsmasq version dnsmasq-2.79-11.el8

Details from Harald:

We discovered an issue introduced in this commit:
137286e9baecf6a3ba97722ef1b49c851b531810

Prior to this commit one could have two dhcp-host entries, one for IPv4
and another for IPv6, for example:

 dhcp-host=52:54:00:bc:c3:fd,172.20.0.11,host2
 dhcp-host=52:54:00:bc:c3:fd,[fd12:3456:789a:1::aadd],host2

This no longer works. In the above example dhcpv6 client succedes, but
the dhcpv4 client get 'no address available'. Swapping the order of the
two entries in the config file allow the dhcpv4 client to succeed, but
then the dhcpv5 client fails.

Alternative configurations that do work in 2.81:

 dhcp-host=52:54:00:bc:c3:fd,172.20.0.11,host2
 dhcp-host=tag:dhcpv6,52:54:00:bc:c3:fd,[fd12:3456:789a:1::aadd],host2

or: 

 dhcp-host=52:54:00:bc:c3:fd,172.20.0.11,[fd12:3456:789a:1::aadd],host2


I'm not sure using two dhcp-host entries was ever intended to work, as
the manual page states that both ipv4 and ipv6 address can be defined
in a single entry.

A first tought for possible fix would be to internally set the
'tag:dhcpv6' for any dhcp-host entry with only ipv6 addresse(s).

It impacts e.g. OpenStack Neutron, see https://bugzilla.redhat.com/show_bug.cgi?id=1829201 for details.
Comment 5 Petr Menšík 2020-05-04 15:11:36 UTC 
Introduced by fix for a bug #1779187.
Comment 18 Petr Menšík 2020-05-11 11:21:58 UTC 
Created attachment 1687258 [details]
Use only matching address family context
Comment 37 errata-xmlrpc 2020-11-04 02:51:58 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (dnsmasq bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4673
Note You need to log in before you can comment on or make changes to this bug.