Bug 1992331
| Summary: | [GSS] [rhel8] SIGSEGV crash after upgrade to RHGS 3.5.4 | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Kaleb KEITHLEY <kkeithle> | |
| Component: | nfs-ganesha | Assignee: | Kaleb KEITHLEY <kkeithle> | |
| Status: | CLOSED ERRATA | QA Contact: | Sri Vignesh Selvan <sselvan> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | rhgs-3.5 | CC: | anrobins, arjsharm, bcotton, dang, ffilz, grajoria, kkeithle, mbenjamin, mhackett, mmuench, msaini, pprakash, rcyriac, rhs-bugs, shilpsha, skoduri, slenzen, sselvan, steved | |
| Target Milestone: | --- | Flags: | bcotton:
needinfo+
|
|
| Target Release: | RHGS 3.5.z Batch Update 7 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | 3.5.5 | |||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
Previously, when a program tried to dereference a null pointer an uncommon condition occurred. It received multiple lock requests where some requests were blocked as the client info from the NLM subsys that required building a lease_id was not present. With this update, the client information from the NLM subsys is provided when possible.
|
Story Points: | --- | |
| Clone Of: | 1959129 | |||
| : | 1995674 (view as bug list) | Environment: | ||
| Last Closed: | 2021-10-05 07:57:33 UTC | Type: | --- | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
|
Comment 13
Kaleb KEITHLEY
2021-08-30 12:16:44 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 (nfs-ganesha bug fix update), 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/RHBA-2021:3727 We have reached the 'Change complete (Testable) deadline in the Fedora Linux 36 release schedule. At this time, all Changes should be complete enough to be testable. Indicate this by setting this tracking bug to MODIFIED. If the code for this Change is fully complete, you can set the status to ON_QA. The next milestone is the Change complete (100% complete) deadline on 2022-02-22 We have reached the 'Change complete (Testable) deadline in the Fedora Linux 36 release schedule. At this time, all Changes should be complete enough to be testable. Indicate this by setting this tracking bug to MODIFIED. If the code for this Change is fully complete, you can set the status to ON_QA. The next milestone is the Change complete (100% complete) deadline on 2022-02-22 We have reached the 'Change complete (Testable) deadline in the Fedora Linux 36 release schedule. At this time, all Changes should be complete enough to be testable. Indicate this by setting this tracking bug to MODIFIED. If the code for this Change is fully complete, you can set the status to ON_QA. The next milestone is the Change complete (100% complete) deadline on 2022-02-22 We have reached the 'Change complete (Testable) deadline in the Fedora Linux 36 release schedule. At this time, all Changes should be complete enough to be testable. Indicate this by setting this tracking bug to MODIFIED. If the code for this Change is fully complete, you can set the status to ON_QA. The next milestone is the Change complete (100% complete) deadline on 2022-02-22 We have reached the 'Change complete (Testable) deadline in the Fedora Linux 36 release schedule. At this time, all Changes should be complete enough to be testable. Indicate this by setting this tracking bug to MODIFIED. If the code for this Change is fully complete, you can set the status to ON_QA. The next milestone is the Change complete (100% complete) deadline on 2022-02-22 We have reached the 'Change complete (Testable) deadline in the Fedora Linux 36 release schedule. At this time, all Changes should be complete enough to be testable. Indicate this by setting this tracking bug to MODIFIED. If the code for this Change is fully complete, you can set the status to ON_QA. The next milestone is the Change complete (100% complete) deadline on 2022-02-22 We have reached the 'Change complete (Testable) deadline in the Fedora Linux 36 release schedule. At this time, all Changes should be complete enough to be testable. Indicate this by setting this tracking bug to MODIFIED. If the code for this Change is fully complete, you can set the status to ON_QA. The next milestone is the Change complete (100% complete) deadline on 2022-02-22 We have reached the 'Change complete (Testable) deadline in the Fedora Linux 36 release schedule. At this time, all Changes should be complete enough to be testable. Indicate this by setting this tracking bug to MODIFIED. If the code for this Change is fully complete, you can set the status to ON_QA. The next milestone is the Change complete (100% complete) deadline on 2022-02-22 We have reached the 'Change complete (Testable) deadline in the Fedora Linux 36 release schedule. At this time, all Changes should be complete enough to be testable. Indicate this by setting this tracking bug to MODIFIED. If the code for this Change is fully complete, you can set the status to ON_QA. The next milestone is the Change complete (100% complete) deadline on 2022-02-22 We have reached the 'Change complete (Testable) deadline in the Fedora Linux 36 release schedule. At this time, all Changes should be complete enough to be testable. Indicate this by setting this tracking bug to MODIFIED. If the code for this Change is fully complete, you can set the status to ON_QA. The next milestone is the Change complete (100% complete) deadline on 2022-02-22 Sorry for the noise, I meant to be testing this against the staging server but forgot to update. Please ignore me. |