clone_image does not update provider_location

Bug #1200708 reported by Navneet on 2013-07-12
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

The method clone_image does not return provider_location for the new volume made by cloning given image. Due to this cinder restart, in case of volumes present by cloning image, will error out as mount for volumes share fails. Also volume deletion leaves such volumes dangling in nfs share although it reports success in cinder client and cleans from database. The method clone_image needs to return a tuple (provider_location, cloned) to the manager.

Navneet (singn) on 2013-07-12
Changed in cinder:
assignee: nobody → Navneet (singn)

Fix proposed to branch: master

Changed in cinder:
status: New → In Progress

Submitter: Jenkins
Branch: master

commit 632cdeca7923b7a06c3d7537b89a21d1790f230d
Author: Navneet Singh <email address hidden>
Date: Sat Jul 13 12:25:30 2013 +0530

    Clone_image should return dict of vol properties, clone status.

    The method will work fine in case of drivers not dependent
    on volume properties like provider_location. It will fail to
    restart in case of nfs drivers and also leave volume created as
    result of clone_image functionality created in the
    nfs share in dangling state after deletion as provider_location
    is None. This fix requires dict of volume properties, cloned status
    to be returned which facilitates passing back provider_location
    in case of nfs drivers and hence resolves the issue.

    bug 1200708

    Change-Id: I590571e52d1c64b6dba7d7e76cd71badd74e51d1

Changed in cinder:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2013-09-05
Changed in cinder:
milestone: none → havana-3
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2013-10-17
Changed in cinder:
milestone: havana-3 → 2013.2
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers