Bug 1861333
| Summary: | Backport: BIND unresponsive during large IXFR and RPZ transfers fix | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Apurbita Mukherjee <apmukher> | ||||
| Component: | bind | Assignee: | Petr Menšík <pemensik> | ||||
| Status: | CLOSED MIGRATED | QA Contact: | qe-baseos-daemons | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 8.2 | CC: | amarirom, mpoole, pemensik, robe | ||||
| Target Milestone: | rc | Keywords: | MigratedToJIRA, Triaged | ||||
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2023-09-21 17:55:26 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: | 1771008 | ||||||
| Attachments: |
|
||||||
|
Description
Apurbita Mukherjee
2020-07-28 10:14:29 UTC
Hello. There is currently no plan to update BIND in RHEL-8 to 9.16 version. The description explicitly mentions an issue with RPZ, which has been fixed in 9.16. It this the fix that the customer is looking for? More preferred option at this point, than updating BIND to 9.16, would be to backport the fix to the current RHEL-8 version of BIND. Would that be sufficient for the customer? A backport would be enough. We don't need any new features, just the assurance that Bind won't stop working when there's a big/complex RPZ update and RPZ rules are in use. If you can fix that with a backport, we'll be all for it. (In reply to robe from comment #3) > A backport would be enough. We don't need any new features, just the > assurance that Bind won't stop working when there's a big/complex RPZ update > and RPZ rules are in use. If you can fix that with a backport, we'll be all > for it. Thank you for the information. Would you be willing to eventually verify the backported fix with a testing package? I'll have to consult with our customer, but I'm quite sure we'll find a way. So, yes, I think we'll be able to verify the fix with a testing package. Upstream commit [1] updates only 9.16 line of BIND. BIND 9.11 was not updated by this change. 1. https://gitlab.isc.org/isc-projects/bind9/commit/6c379655d94bb7daf78b65e8ba0976900c48484b Okay, I am not sure whether backporting this fix would be possible. Mentioned fix added more steps into removing of entries from the database. However, current 9.11 does not even contain more steps when updating new entries. Its basic prerequisite is commit [1], which modified RPZ subsystem in 9.12 release. These changes pile on top of that. I am unsure how many changes it would require to current version, in order to provide better responses during RPZ zone updates. BIND 9.11 seems to make changes in dns_rpz_ready function, which is obsolete in 9.16. Backport would be a lot bigger than initially mentioned commit. 1. https://gitlab.isc.org/isc-projects/bind9/commit/fa9b4de7166479fa5d2708921bd13eb98d95acd7 Created attachment 1713359 [details]
journal-stats
Extract basic statistics from journal file.
Suggested usage:
named-journalprint $F | python journal-stats.py | sort -n | tail
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. 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. |