Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionJaroslav Suchanek
2019-04-09 16:25:38 UTC
+++ This bug was initially created as a clone of Bug #1690702 +++
This bug was initially created as a copy of Bug #1679528
I am copying this bug because:
IBM GPFS is a shared fs supported in rhos: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/11/html/configuration_reference/ch_configuring-openstack-shared-file-systems
However, libvirt in rhel doesn't vm migration in GPFS directly. It is better to support it in RHEL. We have encounter 2 similiar issues before:
1. cephfs: https://bugzilla.redhat.com/show_bug.cgi?id=1672178
2. glusterfs.fuse: https://bugzilla.redhat.com/show_bug.cgi?id=1640465
Description of problem:
Live-migration fail with message "error: Unsafe migration: Migration without shared storage is unsafe" when IBM GPFS (Spectrum Scale) is used as shared file system.
Version-Release number of selected component: 4.5.0-10.el7_6.3.x86_64
How reproducible:
Install 2 nodes CentOS 7.6 with last release of libvirt
Install and mount on both nodes GPFS shared file system.
On first node create a vm with disk type file and source file on shared filesystem.
Live migrate the vm on second node.
Steps to Reproduce:
1. yum install libvirtd
2. virsh create vm.xml
3. virsh migrate --live vm qemu+ssh://second.node/system
Actual results:
error: Unsafe migration: Migration without shared storage is unsafe
Expected results:
no error
Additional info:
If I use the option --unsafe the live-migration works fine. But it isn't the expected behavior.
This impact with our OpenStack environment base con Rocky release
--- Additional comment from Jaroslav Suchanek on 2019-04-09 18:18:12 CEST ---
Per comment https://bugzilla.redhat.com/show_bug.cgi?id=1679528#c3 this is already pushed upstream.
commit d163b940a73a0d6b8277a4bccef2b60936933cf0
Author: Diego Michelotto <diego.michelotto.it>
Date: Mon Feb 25 19:19:03 2019 +0100
virfile: added GPFS as shared fs
Added GPFS as shared file system recognized during live migration
security checks.
GPFS is 'IBM General Parallel File System' also called
'IBM Spectrum Scale'
BUG: https://bugzilla.redhat.com/show_bug.cgi?id=1679528
Signed-off-by: Diego Michelotto <diego.michelotto.it>
Signed-off-by: Peter Krempa <pkrempa>
I will clone this to rhel-8 as well.
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.
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