:37 AM
To: "openstack-dev@lists.openstack.org
<mailto:openstack-dev@lists.openstack.org>"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [cinder] Taskflow 0.10.0 incompatible with
NetApp NFS drivers
GlusterFS CI job is still failing with the same issue.
enstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [cinder] Taskflow 0.10.0 incompatible with NetApp
NFS drivers
GlusterFS CI job is still failing with the same issue.
I gave couple of "recheck"s on [1], after
https://review.openstack.org/#/c/181288/ patch got merged
GlusterFS CI job is still failing with the same issue.
I gave couple of "recheck"s on [1], after
https://review.openstack.org/#/c/181288/ patch got merged.
But still GlusterFS CI job is failing with below error [2]:
ObjectDereferencedError: Can't emit change event for attribute
'Volume.provid
Alright, it was as I had a hunch for, a small bug found in the new
algorithm to make the storage layer
copy-original,mutate-copy,save-copy,update-original (vs
update-original,save-original) more reliable.
https://bugs.launchpad.net/taskflow/+bug/1452978 opened and a one line
fix made @ https:
Are we sure this is taskflow? I'm wondering since those errors are more
from task code (which is in cinder) and the following seems to be a
general garbage collection issue (not connected to taskflow?):
'Exception during message handling: Can't emit change event for
attribute 'Volume.provider_
So it seems that this will break a number of drivers, I see that glusterfs
does the same thing.
On Thu, May 7, 2015 at 10:29 PM, Alex Meade wrote:
> It appears that the release of taskflow 0.10.0 exposed an issue in the
> NetApp NFS drivers. Something changed that caused the sqlalchemy Volume
>
It appears that the release of taskflow 0.10.0 exposed an issue in the
NetApp NFS drivers. Something changed that caused the sqlalchemy Volume
object to be garbage collected even though it is passed into create_volume()
An example error can be found in the c-vol logs here:
http://dcf901611175aa43
