OpenStack Compute (nova)

nbd mounter does not respect max_nbd_devices

Bug #1088073 reported by Michael Still
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Critical
Michael Still
OpenStack Compute (nova) 2013.1 "grizzly"

Bug Description

The _DEVICES list in nova/virt/disk/mount/nbd.py is initialized based on the value of CONF.max_nbd_devices _before_ configuration is parsed.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/17743

Changed in nova:
status: Triaged → In Progress
Michael Still (mikal)
tags: added: folsom-backport-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/17743
Committed: http://github.com/openstack/nova/commit/260dd4f1c714486634422254c6c1163696d43bfb
Submitter: Jenkins
Branch: master

commit 260dd4f1c714486634422254c6c1163696d43bfb
Author: Michael Still <email address hidden>
Date: Sun Dec 9 10:48:28 2012 +1100

    Make the nbd mounter respect CONF.max_nbd_devices.

    We need to wait for the config parser to have been run before we
    query the value of the max_nbd_devices flag. We will always get
    the default value with the previous implementation.

    Based on a conversation with Robert Collins. Resolves bug 1088073.

    Change-Id: If7b5d6a5c7d8153530e97532aad67c42e744ffec

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
milestone: none → grizzly-2
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: grizzly-2 → 2013.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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