Failure to talk to glance registry, leaves stale chunks in swift

Bug #1254497 reported by Iccha Sethi
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Glance
Fix Released
Medium
Zhi Yan Liu

Bug Description

(1)Nova sends data for upload to glance api
(2) glance api sets image status to saving and starts data upload
(3) after data upload, glance api tries to make http call to glance registry to update image status and it gets connection failure.
(4) this percolates as 500 to xen. Image is stuck in saving state
(5) the hypervisor tries to re-upload image, but receives a 409 since image is stuck in saving state

As a result there is left over image data in containers.

Feilong Wang (flwang)
Changed in glance:
assignee: nobody → Fei Long Wang (flwang)
Feilong Wang (flwang)
Changed in glance:
status: New → In Progress
Changed in glance:
status: In Progress → Triaged
Feilong Wang (flwang)
Changed in glance:
status: Triaged → In Progress
Revision history for this message
Ashwini Shukla (ashwini-shukla) wrote :

Hi Fei, just wanted to check with you if you are actively working on this issue. If not could you please reassign this?

Thanks
Ashwini

Revision history for this message
Feilong Wang (flwang) wrote :

Ashwini, I was distracted recently by some other urgent bugs. I'm OK if you want to take it. Now I can clear the assignee.

Changed in glance:
assignee: Fei Long Wang (flwang) → nobody
status: In Progress → Triaged
Zhi Yan Liu (lzy-dev)
Changed in glance:
assignee: nobody → Zhi Yan Liu (lzy-dev)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to glance (master)

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

Changed in glance:
status: Triaged → In Progress
Revision history for this message
Zhi Yan Liu (lzy-dev) wrote :
tags: added: juno-rc-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to glance (master)

Reviewed: https://review.openstack.org/121072
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=aa108f0a7d3cc2a2a5cfb4f70ab59f9ad7aa8707
Submitter: Jenkins
Branch: master

commit aa108f0a7d3cc2a2a5cfb4f70ab59f9ad7aa8707
Author: Zhi Yan Liu <email address hidden>
Date: Fri Sep 12 20:02:27 2014 +0800

    Remove stale chunks when failed to update image to registry

    For image v1 api, the operation of uploading image bits to store and
    the operation of updating image metadata are separaed, so when the
    second operation failed, the image stale chunks will be leaked in store.
    This change added a logic to remove those chunks if an exception
    happenned during the step of image metadata updating. And if
    glance-registry could be reached still, the image status will be changed
    to 'killed', this followed standard glance image status transition.

    Closes-bug: 1254497
    Change-Id: I01e13066b48a8feb1ead0de64992e7997feafdea
    Signed-off-by: Zhi Yan Liu <email address hidden>

Changed in glance:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in glance:
milestone: none → juno-rc2
importance: Undecided → Medium
tags: removed: juno-rc-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to glance (proposed/juno)

Fix proposed to branch: proposed/juno
Review: https://review.openstack.org/127246

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to glance (proposed/juno)

Reviewed: https://review.openstack.org/127246
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=fdcc5c4519bd71b9912ad6c0c7562ef51e774523
Submitter: Jenkins
Branch: proposed/juno

commit fdcc5c4519bd71b9912ad6c0c7562ef51e774523
Author: Zhi Yan Liu <email address hidden>
Date: Fri Sep 12 20:02:27 2014 +0800

    Remove stale chunks when failed to update image to registry

    For image v1 api, the operation of uploading image bits to store and
    the operation of updating image metadata are separaed, so when the
    second operation failed, the image stale chunks will be leaked in store.
    This change added a logic to remove those chunks if an exception
    happenned during the step of image metadata updating. And if
    glance-registry could be reached still, the image status will be changed
    to 'killed', this followed standard glance image status transition.

    Closes-bug: 1254497
    Change-Id: I01e13066b48a8feb1ead0de64992e7997feafdea
    Signed-off-by: Zhi Yan Liu <email address hidden>

Changed in glance:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in glance:
milestone: juno-rc2 → 2014.2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to glance (master)

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to glance (master)
Download full text (14.4 KiB)

Reviewed: https://review.openstack.org/128928
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=858cd9d4fdf32b4cc52e02ec771d01bfb463aa77
Submitter: Jenkins
Branch: master

commit 96e28428655aa7122ed74b045ff1bda1984255b1
Author: Nikhil Komawar <email address hidden>
Date: Tue Oct 14 13:09:48 2014 -0400

    Fix options and their groups - etc/glance-api.conf

    As per the docs at [0] , some of the options should have been moved
    around in the etc/glance-api.conf. This patch changes the conf file to:

        1. indicate new default values
        2. change the group of some of the configs in order to adhere to
           new groups as expected by the deployer.
        3. deprecated configs have been removed or replaced with new ones.

    [0] http://docs.openstack.org/trunk/config-reference/content/glance-conf-changes-master.html

    Fixes bug: 1380689

    Change-Id: I5b5ab96b050b502007e6660a7a613e252404d4e8

commit 9b176a278116849c8f7b7f4d9a987f37ec52779c
Author: Andy McCrae <email address hidden>
Date: Sat Oct 11 20:56:36 2014 +0100

    Adjust authentication.rst doc to reference "identity_uri"

    The "auth_port", "auth_host", and "auth_protocol" variables were
    deprecated in favour of a single "identity_uri" variable.

    * Adjust authentication.rst doc to reference "identity_uri"

    Change-Id: I48de53f21b8d767b276858ed274066015d765f0e
    Closes-Bug: #1361613

commit 08f83f543bc992ae8f2787fb405e58c33dadba73
Author: Jamie Lennox <email address hidden>
Date: Wed Aug 6 18:24:05 2014 +1000

    Use identity_uri instead of older fragments

    This has been the default option in middleware for a while now and we
    should recommend the default options.

    Change-Id: Ief347c897cf15ab4101936a56404e3a378021b15
    (cherry picked from commit e7110a9c6e0119b3d0c6f5cdb3b9675a82b76039)

commit c0d90a580f87dbbf71e3a5d5c1b5cf8d7c7245b2
Author: Stuart McLaren <email address hidden>
Date: Wed Jul 16 13:33:32 2014 +0000

    Prevent setting swift+config locations

    Forbid setting 'swift+config' locations in a similar
    manner to 'file' for security reasons; knowledge of
    the reference name should not be exploitable.

    Setting swift+config had been prevented when swift
    was the default store, this patch changes to forbid
    setting no matter which store is the default.

    As with change id I75af34145521f533dcd6f5fd7690f5a68f3b44b3
    this is v1 only for now.

    Change-Id: I62c4980bd5c2f3dd77fc40cd007bc1067eca63a4
    Closes-bug: 1334196

commit f259cac74d3e988b4012dcc2abd30091df27f5ce
Author: Wayne Okuma <email address hidden>
Date: Wed Oct 8 08:17:20 2014 -0700

    Metadef schema column name is a reserved word in MySQL

    The metadef_properties and metadef_objects tables both have
    a column named schema. Unfortunately, schema is a reserved word
    in some relational database products, including MySQL and PostgreSQL.
    The metadef_properties.schema and metadef_objects.schema
    columns should be renamed to a non reserved word.

    Conflicts:
     glance/db/sqlalchemy/metadata.py
     glance/tests/unit/test_m...

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.