Bug 1581729
Summary: | [OSP13] Neutron denied running dhcp_release6 | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Lon Hohberger <lhh> |
Component: | openstack-selinux | Assignee: | Lon Hohberger <lhh> |
Status: | CLOSED ERRATA | QA Contact: | Udi Shkalim <ushkalim> |
Severity: | urgent | Docs Contact: | |
Priority: | high | ||
Version: | 13.0 (Queens) | CC: | bcafarel, bhaley, jjoyce, jschluet, mgrepl, srevivo |
Target Milestone: | rc | Keywords: | AutomationBlocker, Triaged |
Target Release: | 13.0 (Queens) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-selinux-0.8.14-11.el7ost | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-06-27 13:57:08 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1547669 |
Description
Lon Hohberger
2018-05-23 13:49:02 UTC
dhcp_release6 is something neutron could call to try and clean-up stale leases, so it should be allowed. Since it's not something that would happen often, and it's IPv6 which doesn't have as small a subnet size as IPv4, I wouldn't necessarily consider it a blocker for GA. And it is probably just causing a runtime error in the dhcp-agent, which should be caught correctly. May be related to #1547669 (now dhcp_release6 binary is found and can be called) Yes, Bernard is correct, dhcp_release6 was added in dnsmasq version 2.76, http://www.thekelleys.org.uk/dnsmasq/CHANGELOG - so that script is new to any OSP release that gets it. Linky: bug 1547669 AVC regression tests for this passed; the AVC does not appear with current openstack-selinux-0.8.14-11.el7ost and later 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. https://access.redhat.com/errata/RHEA-2018:2086 |