Bug 1496768 - pool-refresh hangs if NFS/iscsi storage is offline, blocking all pool operations
Summary: pool-refresh hangs if NFS/iscsi storage is offline, blocking all pool operations
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-28 10:47 UTC by Dmitriy S
Modified: 2024-12-17 12:22 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-12-17 12:22:34 UTC
Embargoed:


Attachments (Terms of Use)
libvirtd.log (41.63 KB, text/plain)
2017-09-28 10:47 UTC, Dmitriy S
no flags Details

Description Dmitriy S 2017-09-28 10:47:22 UTC
Created attachment 1331921 [details]
libvirtd.log

Description of problem:
Libvirt hang if the pool defined in it is not active. It was checked on iSCSI and NFS storages. GDB hang too, if you try to connect to the process.

Version-Release number of selected component (if applicable):
libvirtd --version
libvirtd (libvirt) 3.2.0
virsh -v 3.2.0
Reproduced in the same way on version 3.7.0

Steps to Reproduce:
1. virsh pool-create define
<pool type='netfs'>
  <name>NFS</name>
  <uuid>0eb41040-dd23-4d0b-aa59-999b2a9aa2e8</uuid>
  <capacity unit='bytes'>24897585152</capacity>
  <allocation unit='bytes'>1155137536</allocation>
  <available unit='bytes'>23742447616</available>
  <source>
    <host name='0.0.0.0'/>
    <dir path='/nfs-pool'/>
    <format type='auto'/>
  </source>
  <target>
    <path>/nfs-pool</path>
    <permissions>
      <mode>0755</mode>
      <owner>0</owner>
      <group>0</group>
    </permissions>
  </target>
</pool>
2. Turn off the physical machine on which the storage is located.
3. virsh pool-refresh NFS

Actual results:
After that, any actions with pools in the virsh are not available. Other actions like virsh list is available.

Additional info:
After the storage is turned on, the libvirtd continues its normal operation
Libvirtd log at the time of the problem is attached.

Comment 1 Daniel Berrangé 2024-12-17 12:22:34 UTC
Thank you for reporting this issue to the libvirt project. Unfortunately we have been unable to resolve this issue due to insufficient maintainer capacity and it will now be closed. This is not a reflection on the possible validity of the issue, merely the lack of resources to investigate and address it, for which we apologise. If you none the less feel the issue is still important, you may choose to report it again at the new project issue tracker https://gitlab.com/libvirt/libvirt/-/issues The project also welcomes contribution from anyone who believes they can provide a solution.


Note You need to log in before you can comment on or make changes to this bug.