Bug 2249958 - update nfs-ganesha to V5.6 in RHCS 6.1 z3
Summary: update nfs-ganesha to V5.6 in RHCS 6.1 z3
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: NFS-Ganesha
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 6.1z3
Assignee: Frank Filz
QA Contact: Manisha Saini
Disha Walvekar
URL:
Whiteboard:
Depends On:
Blocks: 2247624
TreeView+ depends on / blocked
 
Reported: 2023-11-16 03:45 UTC by tserlin
Modified: 2024-04-11 04:25 UTC (History)
6 users (show)

Fixed In Version: nfs-ganesha-5.6-0.4.el9cp
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Important: if this rebase also contains *enhancements* (or contains only enhancements), select the correct option from the Doc Type drop-down list. Rebase package(s) to version: nfs-ganesha-5.6 Highlights and important bug fixes: Fixes several minor bugs and sync with the version in Ceph 7.0
Clone Of:
Environment:
Last Closed: 2023-12-12 13:56:11 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-7920 0 None None None 2023-11-16 03:46:05 UTC
Red Hat Product Errata RHSA-2023:7740 0 None None None 2023-12-12 13:56:15 UTC

Description tserlin 2023-11-16 03:45:23 UTC
We're updating the nfs-ganesha build in 6.1 z3 to V5.6 (plus some downstream patches).

On top of the upstream V5.6 tag, we've added:

* FSAL's state_free function called by free_state doesn't actually free
* CEPH: Fix up cmount_path
* CEPH: Currently client_oc true is broken, force it to false

See: https://gitlab.cee.redhat.com/ceph/nfs-ganesha/-/commits/ceph-6.1-rhel-patches

This is in line with the nfs-ganesha build for Ceph 7.0.

Comment 1 RHEL Program Management 2023-11-16 03:45:34 UTC
Please specify the severity of this bug. Severity is defined here:
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity.

Comment 13 tserlin 2023-12-06 22:34:14 UTC
The downstream nfs-ganesha build scheduled for the 6.1 z3 release is nfs-ganesha-5.6-0.4.el9cp:

https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=2780987

It is based on the upstream V5.6 tag, plus three downstream-only commits on top of V5.6:

- FSAL's state_free function called by free_state doesn't actually free
- CEPH: Fix up cmount_path
- CEPH: Currently client_oc true is broken, force it to false


Thomas

Comment 14 Frank Filz 2023-12-07 00:01:10 UTC
That looks good on what code is being included and the doc text looks fine.

Comment 16 Frank Filz 2023-12-12 00:55:49 UTC
OK, that isn't quite right.

The update is to V5.6 which includes enhancements and bug fixes, and then on top of V5.6 are three more bug fixes.

I'm not sure what enhancements have already been documented for having previously included V5.1 in 6.1

I think given the short runway of response, please use Tom Serlin's text:

It is based on the upstream nfs-ganesha V5.6 tag which includes enhancements and bug fixes, plus three additional bug fixes:

- FSAL's state_free function called by free_state doesn't actually free
- CEPH: Fix up cmount_path
- CEPH: Currently client_oc true is broken, force it to false

Then at least someone can look to see what enhancements are in Ganesha.

If there is more time, I can provide a more detailed list of enhancements and bug fixes, especially if I know what we have already documented for the rebase to V5.1.

Comment 18 errata-xmlrpc 2023-12-12 13:56:11 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 (Moderate: Red Hat Ceph Storage 6.1 security, enhancements, and 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/RHSA-2023:7740

Comment 19 Red Hat Bugzilla 2024-04-11 04:25:05 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


Note You need to log in before you can comment on or make changes to this bug.