libvirt storage pool does not autostart when using clustered volume group in RHEL 6

Solution Unverified - Updated -

Issue

  • Our libvirt storage pool is not auto starting after server reboot, though it's showing as "Autostart: yes" in the pool info
# virsh vol-list --pool MYPOOL
 error: Failed to list storage volumes 
 error: Requested operation is not valid: storage pool is not active 

# virsh pool-info MYPOOL
 Name: MYPOOL 
 UUID: b61ebcaa-5c9a-c9cf-81a6-0947d0204811 
 State: inactive 
 Persistent: yes 
 Autostart: yes
  • libvirtd fails to activate a storage pool due to a vgchange exit status of 5:
2013-12-02 19:08:08.732+0000: 16153: error : virCommandWait:2304 : internal error Child process (/sbin/vgchange -aly myvg) status unexpected: exit status 5
2013-12-02 19:08:08.733+0000: 16153: error : storageDriverAutostart:101 : Failed to autostart storage pool 'IMAGES': internal error Child process (/sbin/vgchange -aly myvg) status unexpected: exit status 5

Environment

  • Red Hat Enterprise Linux (RHEL) 6 with the Resilient Storage Add On
  • lvm2-cluster
    • One or more volume groups with the clustered attribute set
  • libvirt virtualization
    • One or more storage pools utilizing a clustered volume group

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content