Activity log for bug #1680122

Date Who What changed Old value New value Message
2017-04-05 14:44:37 wangxiyuan bug added bug
2017-04-05 14:45:00 wangxiyuan cinder: assignee wangxiyuan (wangxiyuan)
2017-04-05 14:48:29 wangxiyuan affects cinder tempest
2017-04-05 14:48:29 wangxiyuan tempest: assignee wangxiyuan (wangxiyuan)
2017-04-05 14:48:55 wangxiyuan affects tempest cinder
2017-04-05 14:49:04 wangxiyuan cinder: assignee wangxiyuan (wangxiyuan)
2017-04-05 14:49:26 wangxiyuan bug task added tempest
2017-04-06 08:12:48 Ghanshyam Mann tempest: status New Incomplete
2017-04-14 02:07:03 wangxiyuan tempest: assignee wangxiyuan (wangxiyuan)
2017-04-14 02:21:46 wangxiyuan description This bug is found by tempest test when I use use local user to run the tempest test: reproduce: 1. make sure to use the local user tempest.conf: [auth] use_dynamic_credentials = False test_accounts_file = /opt/stack/tempest/test_auth.yaml test_auth.yaml: - domain_name: Default password: root project_name: admin resources: network: 72b815a6-68ad-4cf4-8b23-6b3fee758f44 username: admin 2. Make sure there are some volumes in Cinder already, and one of the volumes is created from image at least. 3.run the test: tempest.api.volume.test_volumes_list.VolumesListTestJSON.test_volume_list_with_details this test will fail. The reason is that Cinder returned "volume_image_metadata" for each volume even the volume doesn't contain "volume_image_metadata" property. (it will return "volume_image_metadata": {} ) But cinder show {volume_id} doesn't return "volume_image_metadata": {} for an unbootable volume. So the response body format is not the same between list and show API We should drop the empty volume_image_metadata for cinder list IMO. This bug is found by tempest test when I use use local user to run the tempest test: reproduce: 1. make sure to use the local user tempest.conf: [auth] use_dynamic_credentials = False test_accounts_file = /opt/stack/tempest/test_auth.yaml test_auth.yaml: - domain_name: Default   password: root   project_name: admin   resources:     network: 72b815a6-68ad-4cf4-8b23-6b3fee758f44   username: admin 2. Make sure there are some volumes in Cinder already, and one of the volumes is created from image at least. 3.run the test: tempest.api.volume.test_volumes_list.VolumesListTestJSON.test_volume_list_with_details this test will fail. The reason is that Cinder returned "volume_image_metadata" for each volume even the volume doesn't contain "volume_image_metadata" property. (it will return "volume_image_metadata": {} ) But cinder show {volume_id} doesn't return "volume_image_metadata": {} for an unbootable volume. So the response body format is not the same between list and show API We should drop the empty volume_image_metadata for cinder list IMO. Error tests: tempest.api.volume.test_volumes_list.VolumesV2ListTestJSON.test_volume_list_with_details tempest.api.volume.test_volumes_list.VolumesV2ListTestJSON.test_volumes_list_details_by_availability_zone tempest.api.volume.test_volumes_list.VolumesV2ListTestJSON.test_volumes_list_details_by_status
2017-04-14 04:07:38 wangxiyuan description This bug is found by tempest test when I use use local user to run the tempest test: reproduce: 1. make sure to use the local user tempest.conf: [auth] use_dynamic_credentials = False test_accounts_file = /opt/stack/tempest/test_auth.yaml test_auth.yaml: - domain_name: Default   password: root   project_name: admin   resources:     network: 72b815a6-68ad-4cf4-8b23-6b3fee758f44   username: admin 2. Make sure there are some volumes in Cinder already, and one of the volumes is created from image at least. 3.run the test: tempest.api.volume.test_volumes_list.VolumesListTestJSON.test_volume_list_with_details this test will fail. The reason is that Cinder returned "volume_image_metadata" for each volume even the volume doesn't contain "volume_image_metadata" property. (it will return "volume_image_metadata": {} ) But cinder show {volume_id} doesn't return "volume_image_metadata": {} for an unbootable volume. So the response body format is not the same between list and show API We should drop the empty volume_image_metadata for cinder list IMO. Error tests: tempest.api.volume.test_volumes_list.VolumesV2ListTestJSON.test_volume_list_with_details tempest.api.volume.test_volumes_list.VolumesV2ListTestJSON.test_volumes_list_details_by_availability_zone tempest.api.volume.test_volumes_list.VolumesV2ListTestJSON.test_volumes_list_details_by_status This bug is found by tempest test when I use use local user to run the tempest test: reproduce: 1. make sure to use the local user tempest.conf: [auth] use_dynamic_credentials = False test_accounts_file = /opt/stack/tempest/test_auth.yaml test_auth.yaml: - domain_name: Default   password: root   project_name: admin   resources:     network: 72b815a6-68ad-4cf4-8b23-6b3fee758f44   username: admin 2. Make sure there are some volumes in Cinder already, and one of the volumes is created from image at least. 3.run the test: tempest.api.volume.test_volumes_list.VolumesListTestJSON.test_volume_list_with_details this test will fail. The reason is that Cinder returned "volume_image_metadata" for each volume even the volume doesn't contain "volume_image_metadata" property. (it will return "volume_image_metadata": {} ) But cinder show {volume_id} doesn't return "volume_image_metadata": {} for an unbootable volume. So the response body format is not the same between list and show API We should drop the empty volume_image_metadata for cinder list IMO. Error tests: tempest.api.volume.test_volumes_list.VolumesV2ListTestJSON.test_volume_list_with_details tempest.api.volume.test_volumes_list.VolumesV2ListTestJSON.test_volumes_list_details_by_availability_zone tempest.api.volume.test_volumes_list.VolumesV2ListTestJSON.test_volumes_list_details_by_status tempest.api.volume.test_volumes_list.VolumesV2ListTestJSON.test_volumes_list_details_by_bootable
2017-04-14 08:52:22 OpenStack Infra tempest: status Incomplete In Progress
2017-04-19 10:24:37 OpenStack Infra cinder: status New In Progress
2017-05-17 20:09:01 OpenStack Infra cinder: status In Progress Fix Released
2017-05-18 01:21:25 wangxiyuan tempest: status In Progress Invalid