← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1973631] Re: List call for metadef namespaces returns 404 not found while fetching resource_types

 

Reviewed:  https://review.opendev.org/c/openstack/glance/+/841970
Committed: https://opendev.org/openstack/glance/commit/35e6c57bc90365796f45ada9271e532068557b8a
Submitter: "Zuul (22348)"
Branch:    master

commit 35e6c57bc90365796f45ada9271e532068557b8a
Author: Dan Smith <dansmith@xxxxxxxxxx>
Date:   Mon May 16 11:58:05 2022 -0700

    Fix failing namespace list delete race
    
    If a namespace is deleted by another client while we are doing a
    namespace list operation, we will fail the list with NotFound if we
    try to pull the resource_type_associations list. The latter re-queries
    the DB for the namespace and will raise NotFound to us. This is
    especially bad because the namespace being deleted need not even
    belong to the caller of the list, as is the case in a tempest run.
    
    This makes us catch the failure and continue the operation, reporting
    no associations so that the client gets a consistent view and no
    error.
    
    Closes-Bug: #1973631
    Change-Id: I09fc9164a08f42507d2aec44c5b382a72f232571


** Changed in: glance
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1973631

Title:
  List call for metadef namespaces returns 404 not found while fetching
  resource_types

Status in Glance:
  Fix Released

Bug description:
  We encountered this issue in our glance-tempest-plugin
  'test_list_namespace' test, where while running in parallel mode it
  tries to fetch resource_type for a namespace which is actually deleted
  and fails with 404 Not Found error.

  Actually while fetching the resource_types associated with namespace
  if namespace is not exist then it should return empty list rather than
  raising 404 not found from that point.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1973631/+subscriptions



References