How to recover NFS-Ganesha from a failed upgrade during Red Hat Gluster Storage 3.5.3 to Red Hat Gluster Storage 3.5.4 upgrade and Red Hat Enterprise Linux 8.3 to Red Hat Enterprise Linux 8.4 upgrade?

Updated -

This article outlines the procedure to recover NFS-Ganesha from a failed upgrade from Red Hat Gluster Storage 3.5.3 to Red Hat Gluster Storage 3.5.4 upgrade and Red Hat Enterprise Linux 8.3 to Red Hat Enterprise Linux 8.4 upgrade.

The upgrade fails due to the corosync totem token timeout is too short during the upgrade process and the corosync on some nodes is determined incorrectly due...

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content