Bug 1509210
Summary: | dlm: Add ability to recognise multiple source IP addresses per node for the TCP transport | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Steve Whitehouse <swhiteho> |
Component: | kernel | Assignee: | Alexander Aring <aahringo> |
kernel sub component: | DLM | QA Contact: | cluster-qe <cluster-qe> |
Status: | CLOSED WONTFIX | Docs Contact: | |
Severity: | unspecified | ||
Priority: | medium | CC: | aahringo, cfeist, coughlan, dhowells, gfs2-maint, rhandlin, rpeterso, swhiteho, teigland |
Version: | CentOS Stream | Keywords: | FutureFeature, Reopened, Triaged |
Target Milestone: | rc | ||
Target Release: | 8.7 | ||
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: | 2022-07-08 07:27:49 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: | 1509204 | ||
Bug Blocks: |
Description
Steve Whitehouse
2017-11-03 10:54:35 UTC
Is this envisioned as a potential multipath (with a connection per IP) or as a method by which to attempt to reestablish a lost connection with a node and possible round-robin through available IPs? The connection re-establishment is covered in other bugs. This is just to allow the use of multiple IPs per node, which will allow a wider set of network configs. The intention is that they could be used in combination of course. I'm guessing that this one should be a reasonable target for 7.6 ? After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened. Actively being worked on, and patches are going upstream at the moment After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened. Actively being worked on, so reopening. After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened. Reopening again After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened. |