Bug 1698133
Summary: | Live migration fail with unsafe error when GPFS is used as shared filesystem | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Jaroslav Suchanek <jsuchane> |
Component: | libvirt | Assignee: | Peter Krempa <pkrempa> |
Status: | CLOSED ERRATA | QA Contact: | gaojianan <jgao> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 8.0 | CC: | bugproxy, chhu, dyuan, fjin, hannsj_uhl, hhan, jdenemar, jsuchane, knoel, lmen, pkrempa, rbalakri, xuzhang, yalzhang |
Target Milestone: | rc | Keywords: | OtherQA, Patch |
Target Release: | 8.1 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | libvirt-4.5.0-25.el8 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1690702 | Environment: | |
Last Closed: | 2019-11-05 20:48:51 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1679528, 1690702 | ||
Bug Blocks: | 1624641 |
Description
Jaroslav Suchanek
2019-04-09 16:25:38 UTC
For this bug,we can't setup the environment of GPFS,so i can't verify it. Could you please help to verify it when the bug status changes to ON_QA. Thank you ! [Urgent] Hi,could you help to verify this bug on latest version? If you have any questions about setting env,you can give comment here. If not,pls tell me and i will check it with sanity check. Sanity checked in libvirt-debuginfo-4.5.0-30.module+el8.1.0+3574+3a63752b.x86_64 In /src/util/virfile.c ... 3543 # ifndef GPFS_SUPER_MAGIC 3544 # define GPFS_SUPER_MAGIC 0x47504653 3545 # endif ... 3694 if ((fstypes & VIR_FILE_SHFS_GPFS) && 3695 (f_type == GPFS_SUPER_MAGIC)) 3696 return 1; 3697 3698 return 0; 3699 } ... 3861 VIR_FILE_SHFS_CEPH | 3862 VIR_FILE_SHFS_GPFS); ... Have added code into it. 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-2019:3345 |