<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 23, 2014 at 12:40 PM, Nikesh Kumar Mahalka <span dir="ltr"><<a href="mailto:nikeshmahalka@vedams.com" target="_blank">nikeshmahalka@vedams.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>Hi,<br></div>I am able to do all volume operations through dashboard and cli commands.<br></div>But when i am running tempest tests,some tests are getting failed.<br></div><div>For contributing cinder volume driver for my client in cinder,do all tempest tests should passed?<br><br></div><div>Ex:<br>1)<br>./run_tempest.sh tempest.api.volume.test_volumes_snapshots : 1or 2 tests are getting failed<br></div><div><br></div></div></div></blockquote><div><br></div><div>Just as Jay said, to find out what's going wrong you have to tail cinder/nova logs while running tests.</div><div>There are two things you should keep an eye on:</div><div>1. Behaviour (to be clear, does test scenarios coresponds to what actually happening).</div><div>2. Resource utilization (may cause errors because of something went wrong, going back to log analyzation)</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div></div><div>But when i am running individual tests in "test_volumes_snapshots",all tests are getting passed.<br><br>2)<br>./run_tempest.sh tempest.api.volume.test_volumes_actions.VolumesV2ActionsTest.test_volume_upload:<br></div><div>This is also getting failed.<br></div><div><br><br></div><div><br></div>Regards<br></div>Nikesh<br></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Mon, Sep 22, 2014 at 4:12 PM, Ken'ichi Ohmichi <span dir="ltr"><<a href="mailto:ken1ohmichi@gmail.com" target="_blank">ken1ohmichi@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">Hi Nikesh,<br>
<span><br>
> -----Original Message-----<br>
> From: Nikesh Kumar Mahalka [mailto:<a href="mailto:nikeshmahalka@vedams.com" target="_blank">nikeshmahalka@vedams.com</a>]<br>
> Sent: Saturday, September 20, 2014 9:49 PM<br>
> To: <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a>; OpenStack Development Mailing List (not for usage questions)<br>
> Subject: Re: [Openstack] No one replying on tempest issue?Please share your experience<br>
><br>
> Still i didnot get any reply.<br>
<br>
</span>Jay has already replied to this mail, please check the nova-compute<br>
and cinder-volume log as he said[1].<br>
<br>
[1]: <a href="http://lists.openstack.org/pipermail/openstack-dev/2014-September/046147.html" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/2014-September/046147.html</a><br>
<span><br>
> Now i ran below command:<br>
> ./run_tempest.sh tempest.api.volume.test_volumes_snapshots.VolumesSnapshotTest.test_volume_from_snapshot<br>
><br>
> and i am getting test failed.<br>
><br>
><br>
> Actually,after analyzing tempest.log,i found that:<br>
> during creation of a volume from snapshot,tearDownClass is called and it is deleting snapshot bfore creation of volume<br>
> and my test is getting failed.<br>
<br>
</span>I guess the failure you mentioned at the above is:<br>
<br>
2014-09-20 00:42:12.519 10684 INFO tempest.common.rest_client<br>
[req-d4dccdcd-bbfa-4ddf-acd8-5a7dcd5b15db None] Request<br>
(VolumesSnapshotTest:tearDownClass): 404 GET<br>
<a href="http://192.168.2.153:8776/v1/ff110b66c98d455092c6f2a2577b4c80/snapshots/71d3cad4-440d-4fbb-8758-76da17b6ace6" target="_blank">http://192.168.2.153:8776/v1/ff110b66c98d455092c6f2a2577b4c80/snapshots/71d3cad4-440d-4fbb-8758-76da17b6ace6</a><br>
0.029s<br>
<br>
and<br>
<br>
2014-09-20 00:42:22.511 10684 INFO tempest.common.rest_client<br>
[req-520a54ad-7e0a-44ba-95c0-17f4657bc3b0 None] Request<br>
(VolumesSnapshotTest:tearDownClass): 404 GET<br>
<a href="http://192.168.2.153:8776/v1/ff110b66c98d455092c6f2a2577b4c80/volumes/7469271a-d2a7-4ee6-b54a-cd0bf767be6b" target="_blank">http://192.168.2.153:8776/v1/ff110b66c98d455092c6f2a2577b4c80/volumes/7469271a-d2a7-4ee6-b54a-cd0bf767be6b</a><br>
0.034s<br>
<br>
right?<br>
If so, that is not a problem.<br>
VolumesSnapshotTest creates two volumes, and the tearDownClass checks these<br>
volumes deletions by getting volume status until 404(NotFound) [2].<br>
<br>
[2]: <a href="https://github.com/openstack/tempest/blob/master/tempest/api/volume/base.py#L128" target="_blank">https://github.com/openstack/tempest/blob/master/tempest/api/volume/base.py#L128</a><br>
<span><br>
> I deployed a juno devstack setup for a cinder volume driver.<br>
> I changed cinder.conf file and tempest.conf file for single backend and restarted cinder services.<br>
> Now i ran tempest test as below:<br>
> /opt/stack/tempest/run_tempest.sh tempest.api.volume.test_volumes_snapshots<br>
><br>
> I am getting below output:<br>
> Traceback (most recent call last):<br>
> File "/opt/stack/tempest/tempest/api/volume/test_volumes_snapshots.py", line 176, in test_volume_from_snapshot<br>
> snapshot = self.create_snapshot(self.volume_origin['id'])<br>
> File "/opt/stack/tempest/tempest/api/volume/base.py", line 112, in create_snapshot<br>
> 'available')<br>
> File "/opt/stack/tempest/tempest/services/volume/json/snapshots_client.py", line 126, in wait_for_snapshot_status<br>
> value = self._get_snapshot_status(snapshot_id)<br>
> File "/opt/stack/tempest/tempest/services/volume/json/snapshots_client.py", line 99, in _get_snapshot_status<br>
> snapshot_id=snapshot_id)<br>
> SnapshotBuildErrorException: Snapshot 6b1eb319-33ef-4357-987a-58eb15549520 failed to build and is in<br>
> ERROR status<br>
<br>
</span>What happens if running the same operation as Tempest by hands on your<br>
environment like the following ?<br>
<br>
[1] $ cinder create 1<br>
[2] $ cinder snapshot-create <id of the created volume at [1]><br></div></div></blockquote></div></div></blockquote><div>[3] cinder snapshot-show <id for [2]> (see if snapshot was baked properly) </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
[3] $ cinder create --snapshot-id <id of the created snapshot at [2]> 1<br>
[4] $ cinder show <id of the created volume at [3]><br>
<br>
Please check whether the status of created volume at [3] is "available" or not.<br>
<br>
Thanks<br>
Ken'ichi Ohmichi<br>
<br>
_______________________________________________<br></div></div>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
</blockquote></div><br></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div><div class="gmail_extra">Best regards,</div><div class="gmail_extra">Denis Makogon.</div></div>