Red Hat Bugzilla – Bug 1619538
Snapshot status fails with commit failure
Last modified: 2018-09-26 13:07:18 EDT
Description of problem: ======================= Snapshot status fails with commit failure for activated snapshots. This is the case for the activated snapshots which were present after migration from RHEL 6 to RHEL 7 . Clones of these snapshots were also present along with other volumes (from which the snapshots were taken) Version-Release number of selected component (if applicable): ============================================================= glusterfs-3.12.2-16.el7rhgs.x86_64 How reproducible: ================= 2/2 Steps to Reproduce: =================== 1. On RHEL 6 , Create snapshots of a volume and activate them 2. Create clones of these activated snapshots 3. Migrate from RHEL 6 to RHEL 7 4. Perform a " gluster snapshot status <snap-name> "command Actual results: =============== Snapshot status failing with commit failure Expected results: ================= Status of the snapshots should be shown properly Additional info: ================
Root Cause : When OS upgrade is from RHEL6 to RHEL7 there is difference in symlink (/var/run) between these two versions. Basically when (/var/run) is symlinked to /run, mount command resolves path and mounts it. But at the same time call to those functions fails who depends on absolute path. (like strcmp in glusterd_get_mnt_entry_info)
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, 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-2018:2607