[Backport] block device mapping timeout in compute

Bug #1461574 reported by Vitaly Sedelnik
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Invalid
High
MOS Maintenance
5.1.x
Fix Released
High
MOS Maintenance
8.0.x
Invalid
High
MOS Maintenance

Bug Description

This bug is created to track backporting of upstream fix for https://bugs.launchpad.net/nova/+bug/1332382
The backport should be done to 5.1-updates and 5.1.1-upadtes branches only as 6.0+ do have this fix already

Original description:
=================
When booting instances passing in block-device and increasing the volume size , instances can go in to error state if the volume takes longer to create than the hard code value set in:

nova/compute/manager.py

  def _await_block_device_map_created(self, context, vol_id, max_tries=180,
                                        wait_between=1):

Here is the command used to repro:

nova boot --flavor ca8d889e-6a4e-48f8-81ce-0fa2d153db16 --image 438b3f1f-1b23-4b8d-84e1-786ffc73a298
--block-device source=image,id=438b3f1f-1b23-4b8d-84e1-786ffc73a298,dest=volume,size=128
--nic net-id=5f847661-edef-4dff-9f4b-904d1b3ac422 --security-groups d9ce9fe3-983f-42a8-899e-609c01977e32
Test_Image_Instance

max_retries should be made configurable.

Looking through the different releases, Grizzly was 30, Havana was 60 , IceHouse is 180.

Changed in mos:
milestone: 5.1-mu-1 → none
no longer affects: mos
Changed in mos:
status: New → Invalid
importance: Undecided → High
assignee: nobody → MOS Sustaining (mos-sustaining)
no longer affects: mos
description: updated
Revision history for this message
Denis Meltsaykin (dmeltsaykin) wrote :

5.1.1 has already these changes

Revision history for this message
Denis Meltsaykin (dmeltsaykin) wrote :

The fix for 5.1-update is already merged here https://review.fuel-infra.org/#/c/7410/

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.