Cinder volume has error status

Bug #1605116 reported by Ivan Lozgachev on 2016-07-21
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
High
Ivan Lozgachev
8.0.x
High
MOS Maintenance
9.x
High
Ivan Lozgachev

Bug Description

Software: MOS 8.0 MU2

Configuration:
3 controller
178 compute
20 compute + ceph nodes

For some reason Cinder volume became "status": "error" after creation during Rally test NovaServers.boot_server_from_volume_and_delete

Rally report
http://mos-scale.vm.mirantis.net/test_results/build_8.0.0-570/jenkins-10_env_run_rally_custom-251-ubuntu-MSK-2016-07-18-11:28:48-2016-07-20-22:10:03/rally_report.html#/NovaServers.boot_server_from_volume_and_delete/failures

I didn't find any specific errors in Cinder logs. Please analyse attached Cinder logs from controller node. Mostly all info is stored in "cinder-all.log.2.gz" file.

Ivan Lozgachev (ilozgachev) wrote :
Changed in mos:
assignee: nobody → MOS Cinder (mos-cinder)
Changed in mos:
milestone: none → 8.0-updates
importance: Undecided → High
tags: added: scale
Changed in mos:
status: New → Confirmed
Ivan Kolodyazhny (e0ne) wrote :

Please, provide full logs. There are no records in cinder-volumes log for volume '7575d049-9b94-439d-9e89-ee69a8563bcd'

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers