[doc] Make block device mapping timeout configurable

Bug #1441724 reported by OpenStack Infra
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Triaged
Medium
Fuel Documentation Team

Bug Description

https://review.openstack.org/171233
commit a3322f28b5548dd83e89b225b88cf067cf9da43d
Author: Aleksandr Didenko <email address hidden>
Date: Tue Apr 7 17:15:07 2015 +0300

    Make block device mapping timeout configurable

    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 3 minutes (current default value).

    This change adds support for 2 new cluster configutation options:
    - block_device_allocate_retries (default: 300)
    - block_device_allocate_retries_interval (default: 3)

    Thess options are configurable via fuel cli or Hiera. They are added
    to nova.conf on compute nodes and allow to adjust block device
    allocation timeout value.

    DocImpact

    Change-Id: If9148da046d31aab60a13bd70e94700331770000
    Closes-bug: #1280399

Changed in fuel:
assignee: nobody → Fuel Documentation Team (fuel-docs)
importance: Undecided → High
status: New → Confirmed
milestone: none → 6.1
Changed in fuel:
status: Confirmed → Triaged
summary: - Make block device mapping timeout configurable
+ [doc] Make block device mapping timeout configurable
tags: added: docs release-notes
removed: fuel-library
Revision history for this message
Sheena Conant (sheena-conant) wrote :

Is this a workaround or just a known issue?

Changed in fuel:
importance: High → Medium
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.