Hello I verified manila for Noble.
Deployed noble env using Juju * Pre-proposed (1:18.0.1-0ubuntu2.2) - Confirmed buggy order in manager.py remove_export(): L522: self._delete_rados_object(...) # object deleted first L524: self._remove_rados_object_url_from_index(name) - Injected dangling index entry → NFS-Ganesha crashed with FATAL: "cu_rados_url_fetch: Failed reading ... Unknown error -2" "main :NFS STARTUP :FATAL :Fatal errors. Server exiting..." * Post-proposed (1:18.0.1-0ubuntu2.3) - Confirmed fixed order in manager.py remove_export(): L522: self._remove_rados_object_url_from_index(name) # index removed first L523: self._delete_rados_object(...) - Simulated crash between the two operations: index entry removed, object NOT deleted (orphan left behind) → NFS-Ganesha started normally, orphan object ignored - Ganesha baseline: active after upgrade * Packages ii manila-api 1:18.0.1-0ubuntu2.3 all ii manila-common 1:18.0.1-0ubuntu2.3 all ii manila-data 1:18.0.1-0ubuntu2.3 all ii manila-scheduler 1:18.0.1-0ubuntu2.3 all ii manila-share 1:18.0.1-0ubuntu2.3 all ii python3-manila 1:18.0.1-0ubuntu2.3 all ** Tags removed: verification-needed-noble ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2143377 Title: Dangling RADOS export index entry in remove_export() crashes NFS- Ganesha To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2143377/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
