Stale BDM records remain in the DB after n-api to n-cpu RPC timeouts during reserve_block_device_name
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
In Progress
|
Undecided
|
Lee Yarwood |
Bug Description
Description
===========
When attaching block devices n-api will call out to the n-cpu service hosting an instance and attempt to reserve a block device name via reserve_
Steps to reproduce
==================
1. Attach a volume to an instance, ensuring any call to reserve_
Expected result
===============
The RPC timeout is hit and any BDM records created by the n-cpu service are removed by n-api.
Actual result
=============
The RPC timeout is hit but the BDM records persist.
Environment
===========
1. Exact version of OpenStack you are running. See the following
list for all releases: http://
Master.
2. Which hypervisor did you use?
(For example: Libvirt + KVM, Libvirt + XEN, Hyper-V, PowerKVM, ...)
What's the version of that?
N/A
2. Which storage type did you use?
(For example: Ceph, LVM, GPFS, ...)
What's the version of that?
N/A
3. Which networking type did you use?
(For example: nova-network, Neutron with OpenVSwitch, ...)
N/A
Logs & Configs
==============
Invalid bdm record remains when reserve_
https:/
tags: | added: compute |
Fix proposed to branch: master /review. opendev. org/682594
Review: https:/