ooi

Volumes are not properly attached when creating instances

Bug #1679498 reported by Enol Fernández
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ooi
Fix Released
High
Enol Fernández
ooi 1.1.0

Bug Description

Compute instance creation with linked volumes is not properly done and show up in nova as attached but they are not actually linked. Issue seems missing "destination_type" in the block_device_mapping.

Enol Fernández (enolfc)
Changed in ooi:
importance: Undecided → High
assignee: nobody → Enol Fernández (enolfc)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to ooi (master)

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

Changed in ooi:
status: New → In Progress
Alvaro Lopez (aloga)
Changed in ooi:
milestone: none → 1.1.0
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to ooi (master)

Reviewed: https://review.openstack.org/453031
Committed: https://git.openstack.org/cgit/openstack/ooi/commit/?id=571cca37527561b0ebbb0785abb1494fd1f9890b
Submitter: Jenkins
Branch: master

commit 571cca37527561b0ebbb0785abb1494fd1f9890b
Author: Enol Fernandez <email address hidden>
Date: Tue Apr 4 07:50:18 2017 +0100

    Fix block_device_mapping on compute creation

    Use block_device_mapping instead of block_device_mapping_v2 that seems
    to not attach properly volumes on creation. This legacy option is enough
    to support the requested use case (attaching volumes on boot).

    Change-Id: I39f17faec6a48e90740e5e4757c1278df0b9830c
    Closes-bug: #1679498

Changed in ooi:
status: In Progress → Fix Released
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.