Their fix was to add a cleanup call to libvirt - see comment 6 on the Redhat page.
I have been able to reproduce this on a Folsom-2 cluster using Precise by repeatedly adding and removing a volume with the same mountpoint. Strangely, the fault did not show up on all instances I tried it on.
The bug looks identical to one that Redhat recently closed: https:/ /bugzilla. redhat. com/show_ bug.cgi? id=712266
Their fix was to add a cleanup call to libvirt - see comment 6 on the Redhat page.
I have been able to reproduce this on a Folsom-2 cluster using Precise by repeatedly adding and removing a volume with the same mountpoint. Strangely, the fault did not show up on all instances I tried it on.