block_device_mapping redundancy data when mq not routed

Bug #1865125 reported by HYSong
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Expired
Undecided
Unassigned

Bug Description

The volumes_attached has some repetitive volume id when excuting 'openstack server show <server-id>',

and there are same redundancy data in block_device_mapping table.

In this period, not routed error occurred in MQ, and I failed to resize this server.

I don't know whether the MQ cause this redundancy data error.

Revision history for this message
Balazs Gibizer (balazs-gibizer) wrote :

Could you please describe the exact steps that caused the unexpected behavior? Also could you please link to the relevant nova logs around the time of the failed resize and / or the MQ failure?

Changed in nova:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]

Changed in nova:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.