solidfire image cache not auto-creating cache account

Bug #1414760 reported by John Griffith
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
Medium
John Griffith

Bug Description

The standard flow in the SolidFire volume is to create accounts dynamically as needed based on project id. Unfortunately the clone_image method "forgot" about this detail and calls the private clone_volume method without a valid account resulting in an unhandled AccountNotFound Exception.

We should go ahead and create the cache account during the verify clone_image steps, after we've made sure that image caching is enabled.

Changed in cinder:
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → John Griffith (john-griffith)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

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

Changed in cinder:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (master)

Reviewed: https://review.openstack.org/150202
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=a36100bd34a22ddc3b620947809a41d328b1e949
Submitter: Jenkins
Branch: master

commit a36100bd34a22ddc3b620947809a41d328b1e949
Author: John Griffith <email address hidden>
Date: Mon Jan 26 15:21:30 2015 -0700

    Create SolidFire Template account on init

    The standard flow in the SolidFire volume is to create
    accounts dynamically as needed based on project id.
    Unfortunately the clone_image method "forgot" about this
    detail and calls the private clone_volume method without
    a valid account resulting in an AccountNotFound
    Exception.

    The clone_image method is enabled using a specific account
    provided via the configuration file. Rather than worry
    about dynamic account creation on clone_image call, this
    patch just makes it part of the init phase. We check to
    see if template caching is enabled and if it is, just
    go ahead and check/create the account on startup.

    Closes-Bug: #1414760

    Change-Id: I62f3f7aff958c097ae662d21b2c0f55a8d08f784

Changed in cinder:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

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

Thierry Carrez (ttx)
Changed in cinder:
milestone: none → kilo-2
status: Fix Committed → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (master)

Reviewed: https://review.openstack.org/150617
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=4580725ea21ff92ec7b092ad7061d0aac600bc66
Submitter: Jenkins
Branch: master

commit 4580725ea21ff92ec7b092ad7061d0aac600bc66
Author: John Griffith <email address hidden>
Date: Tue Jan 27 16:19:11 2015 -0700

    Create SolidFire Template account on init

    The standard flow in the SolidFire volume is to create
    accounts dynamically as needed based on project id.
    Unfortunately the clone_image method "forgot" about this
    detail and calls the private clone_volume method without
    a valid account resulting in an AccountNotFound
    Exception.

    The clone_image method is enabled using a specific account
    provided via the configuration file. Rather than worry
    about dynamic account creation on clone_image call, this
    patch just makes it part of the init phase. We check to
    see if template caching is enabled and if it is, just
    go ahead and check/create the account on startup.

    Change-Id: I41a8d400d3dfc0e185304f80efd419ebac9efdf6
    Closes-Bug: #1414760

Thierry Carrez (ttx)
Changed in cinder:
milestone: kilo-2 → 2015.1.0
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.