Bug 2046533
| Summary: | nvme-cli: nvme connect-all returns Failed to write to /dev/nvme-fabrics | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Marco Patalano <mpatalan> |
| Component: | nvme-cli | Assignee: | Maurizio Lombardi <mlombard> |
| Status: | CLOSED WONTFIX | QA Contact: | Marco Patalano <mpatalan> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.6 | CC: | arun.c, jbrassow, jmeneghi, thomasberryiif |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | NVMe_P2 | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-07-26 07:28:16 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: | |||
|
Description
Marco Patalano
2022-01-26 21:50:18 UTC
Marco what's the storage array used to find this bug. DellEMC? I think this is a long standing problem that either needs to be fixed upstream, or pushed back to the vendor. I don't think we see this problem with anything but the specific vendors array. Did you manage to fix the write error? I have a similar error, I wonder what you found the solution. Did you manage to fix the write error? I have a similar error, I wonder what you found the solution. I tried searching the internet for solutions, using the essay title maker https://papersowl.com/essay-title-generator/ to generate the right search queries. But so far I have not found the information, and because of this I cannot finish my educational project. Marco, is this still a problem with RHEL 9.2? Can we mark this as fixed in the current release. Note: nvme/tcp is not supported in RHEL 8 Hello John, For RHEL-9.2, I do not see the following messages: Failed to write to /dev/nvme-fabrics: Connection timed out However, for both RHEL-8.8 and RHEL-9.2, I continue to see these messages when issuing "nvme connect-all": # nvme connect-all traddr=172.18.210.60 is already connected traddr=172.18.210.61 is already connected traddr=172.18.220.61 is already connected traddr=172.18.220.60 is already connected As mentioned previously, this may be confusing to customers as we did not establish any connections prior to issuing the command. Finally, for RHEL-8.8, I continue to see the following only when using the Powerstore on the backend: # nvme connect-all Failed to write to /dev/nvme-fabrics: Connection timed out Failed to write to /dev/nvme-fabrics: Connection timed out Failed to write to /dev/nvme-fabrics: Connection timed out Failed to write to /dev/nvme-fabrics: Connection timed out Failed to write to /dev/nvme-fabrics: Connection timed out Failed to write to /dev/nvme-fabrics: Connection timed out Since NVMe-TCP is tech preview in RHEL-8, I am OK with closing this BZ. However, should I open a separate BZ to determine if the messaging for successful connections needs to be fixed? Marco 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. |