On 09/28/2017 12:22 PM, Apoorva Deshpande wrote:
> It appears that Cinder started using NFS locks around Sept 19th. That
> resulted in our CI failures as we don't support it. Tempest tests succeeded
> when we added a nolock option in the NFS configuration[1].
>
> Can someone provide more informati
It appears that Cinder started using NFS locks around Sept 19th. That
resulted in our CI failures as we don't support it. Tempest tests succeeded
when we added a nolock option in the NFS configuration[1].
Can someone provide more information on this change?
Thanks,
Apoorva
[1] http://openstack-c
I patched sos-ci and logs are available now [1]. First exception occurrence
I spot in c-vol.txt is here [2]
[1] http://openstack-ci.tintri.com/tintri/refs-changes-59-507359-1/logs/
[2] http://paste.openstack.org/show/621983/
On Mon, Sep 25, 2017 at 11:32 PM, Silvan Kaiser wrote:
> Hi Apoorva!
>
Hi Apoorva!
The test run is sadly missing the service logs, probably because you're
using a current DevStack (systemd based services) but an older sos-ci
version? If you apply
https://github.com/j-griffith/sos-ci/commit/f0f2ce2e2f2b12727ee5aa75a751376dcc1ea3a4
you should be able to get the logs for
Hello,
Tintri's Cinder CI started failing around Sept 19, 2017. There are 29 tests
failing[1] with following errors [2][3][4]. Tintri Cinder driver inherit
nfs cinder driver and it's available here[5].
Please let me know if anyone has recently seen these failures or has any
pointers on how to fix
