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.
Bug 1436065 - Persistent gluster pool will be in inactive status after libvirtd restarts
Summary: Persistent gluster pool will be in inactive status after libvirtd restarts
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.4
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Peter Krempa
QA Contact: jiyan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-27 05:17 UTC by lijuan men
Modified: 2018-04-10 10:43 UTC (History)
4 users (show)

Fixed In Version: libvirt-3.7.0-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 10:42:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0704 0 None None None 2018-04-10 10:43:05 UTC

Description lijuan men 2017-03-27 05:17:36 UTC 
Description of problem:
Persistent gluster pool will be in inactive status after libvirtd restarts

Version-Release number of selected component (if applicable):
libvirt-3.1.0-2.el7.x86_64
qemu-kvm-rhev-2.8.0-6.el7.x86_64


How reproducible:
100%

Steps to Reproduce:

1.define and start a pool with the following xml:

[root@localhost ~]# cat gluster-pool.xml
<pool type='gluster'>
<name>gluster</name>
<source>
<host name='10.66.70.107'/>
<name>test</name>
<dir path='/'/>
</source>
</pool>


[root@localhost ~]# virsh pool-define gluster-pool.xml
Pool gluster defined from gluster-pool.xml

[root@localhost ~]# virsh pool-start gluster
Pool gluster started


[root@localhost ~]# virsh pool-list --all
 Name                 State      Autostart
-------------------------------------------
 default              active     yes      
 Downloads            active     yes      
 gluster              active     no  


[root@localhost ~]# virsh pool-info gluster
Name:           gluster
UUID:           44900b5b-30c6-46e0-b095-9aa2bb4c8627
State:          running
Persistent:     yes
Autostart:      no
Capacity:       49.98 GiB
Allocation:     4.72 GiB
Available:      45.25 GiB

2.restart libvirtd,and check the status of the gluster pool

[root@localhost ~]# systemctl restart libvirtd

[root@localhost ~]# virsh pool-list --all
 Name                 State      Autostart
-------------------------------------------
 default              active     yes      
 Downloads            active     yes      
 gluster           ** inactive**   no        

Actual results:
the gluster pool is in the inactive status

Expected results:
the gluster pool can always be active as default pool

Additional info:
Comment 2 Peter Krempa 2017-04-05 10:59:31 UTC 
commit a200ebbc6f2cc5835daf0ddda9a347b7311a7877
Author: Peter Krempa <pkrempa>
Date:   Thu Mar 30 13:18:43 2017 +0200

    storage: gluster: Implement 'checkPool' method so that state is restored
    
    After restart of libvirtd the 'checkPool' method is supposed to validate
    that the pool is online. Since libvirt then refreshes the pool contents
    anyways just return whether the pool was supposed to be online so that
    the code can be reached. This is necessary since if a pool does not
    implement the method it's automatically considered as inactive.
Comment 8 errata-xmlrpc 2018-04-10 10:42:33 UTC 
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/RHEA-2018:0704
Note You need to log in before you can comment on or make changes to this bug.