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 information on this change? >
I'm not sure there was a change in Cinder that would result in this error message: Command: /usr/bin/python -m oslo_concurrency.prlimit --as=1073741824 --cpu=8 -- sudo cinder-rootwrap /etc/cinder/rootwrap.conf env LC_ALL=C qemu-img info /opt/stack/data/cinder/mnt/a67d7d4be86399df850bfa711f7837f7/volume-43b54c3e-ae10-47b1-8a43-c9427551f923 Sep 26 12:14:13.919553 303-openstack-test2 cinder-volume[19641]: Exit code: 1 Stderr: u"qemu-img: Could not open '/opt/stack/data/cinder/mnt/a67d7d4be86399df850bfa711f7837f7/volume-43b54c3e-ae10-47b1-8a43-c9427551f923': Failed to lock byte 100\n" You may need to look at what else changed on the system -- qemu-img versions, NFS utilities, etc. > Thanks, > Apoorva > > [1] http://openstack-ci.tintri.com/tintri/refs-changes-09-504009-2/ > > On Tue, Sep 26, 2017 at 1:28 PM, Apoorva Deshpande <apps.d...@gmail.com> > wrote: > >> 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 <sil...@quobyte.com> >> wrote: >> >>> 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-gri >>> ffith/sos-ci/commit/f0f2ce2e2f2b12727ee5aa75a751376dcc1ea3a4 you should >>> be able to get the logs for new test runs. This will help debugging this. >>> Best >>> Silvan >>> >>> >>> >>> 2017-09-26 1:54 GMT+02:00 Apoorva Deshpande <apps.d...@gmail.com>: >>> >>>> 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. >>>> >>>> Thanks, >>>> Apoorva >>>> >>>> IRC: Apoorva >>>> >>>> [1] http://openstack-ci.tintri.com/tintri/refs-changes-57-50 >>>> 5357-1/testr_results.html >>>> [2] http://paste.openstack.org/show/621886/ >>>> [3] http://paste.openstack.org/show/621858/ >>>> [4] http://paste.openstack.org/show/621857/ >>>> [5] https://github.com/openstack/cinder/blob/master/cinder/v >>>> olume/drivers/tintri.py >>>> >>>> ____________________________________________________________ >>>> ______________ >>>> OpenStack Development Mailing List (not for usage questions) >>>> Unsubscribe: openstack-dev-requ...@lists.op >>>> enstack.org?subject:unsubscribe >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>>> >>>> >>> >>> >>> -- >>> Dr. Silvan Kaiser >>> Quobyte GmbH >>> Hardenbergplatz 2, 10623 Berlin - Germany >>> +49-30-814 591 800 <+49%2030%20814591800> - www.quobyte.com<http://www.q >>> uobyte.com/> >>> Amtsgericht Berlin-Charlottenburg, HRB 149012B >>> Management board: Dr. Felix Hupfeld, Dr. Björn Kolbeck, Dr. Jan Stender >>> >>> ____________________________________________________________ __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev