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 1375569 - [RFE] Support for dhcp_release6 on RHEL platform for OSP10
Summary: [RFE] Support for dhcp_release6 on RHEL platform for OSP10
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dnsmasq
Version: 7.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 7.3
Assignee: Petr Menšík
QA Contact: Jan Ščotka
Ioanna Gkioka
Depends On: 1375527
Blocks: 1380362 1393869 1400961 1411884
TreeView+ depends on / blocked
Reported: 2016-09-13 12:41 UTC by Sridhar Gaddam
Modified: 2017-08-01 22:56 UTC (History)
12 users (show)

Fixed In Version: dnsmasq-2.76-1.el7
Doc Type: Enhancement
Doc Text:
*dhcp_release6* now releases IPv6 addresses With this update, the *dhcp_release6* utility can release Dynamic Host Configuration Protocol version 6 (DHCPv6) leases for IPv6 addresses on the local dnsmasq server. See the dhcp_release6(1) man page for more information about the "dhcp_release6" command.
Clone Of:
Last Closed: 2017-08-01 22:56:41 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2117 0 normal SHIPPED_LIVE dnsmasq bug fix and enhancement update 2017-08-01 19:38:28 UTC

Description Sridhar Gaddam 2016-09-13 12:41:12 UTC
Description of problem:
dhcp_release which is part of dnsmasq works only for IPv4 addresses.
For IPv6 addresses, a new utility named, dhcp_release6, is added and is available in stock dnsmasq[1] version 2.76

OpenStack Neutron dhcp-agent invokes [1] dhcp_release6 utility for releasing IPv6 addresses and this feature will be part of OpenStack Newton release (i.e., OSP10). 
This bug is to have the necessary platform support for using dhcp_release6 on RHEL platform.

[1] http://www.thekelleys.org.uk/dnsmasq/CHANGELOG
[2] https://review.openstack.org/#/c/301747/

Additional info:
A missing dhcp_release6 utility will not have impact on IPv4 use-cases but will affect the IPv6 dhcpv6-stateful subnet use-cases.

Comment 1 Nir Yechiel 2016-09-13 12:47:42 UTC
To clarify, RHOSP 10 is planned to be shipped on top of RHEL 7.3.

@Pavel, can you please review this bug? This is pretty important to us on the OpenStack side as this could break our support for IPv6.


Comment 22 errata-xmlrpc 2017-08-01 22:56:41 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, and where to find the updated
files, follow the link below.

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


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