block_device_mapping redundancy data when mq not routed
Bug #1865125 reported by
HYSong
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_
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 | #1 |
| Changed in nova: | |
| status: | New → Incomplete |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in nova: | |
| status: | Incomplete → Expired |
To post a comment you must log in.
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?