Excessive "Deleting stale allocation for instance" warnings in nova-compute logs

Bug #1693903 reported by Matt Riedemann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Medium
Matt Riedemann
Newton
New
Undecided
Unassigned
Ocata
Fix Committed
Medium
Lee Yarwood

Bug Description

I noticed this here:

https://review.openstack.org/#/c/460177/12/nova/compute/resource_tracker.py

Which is part of a refactor, and that warning actually goes back to newton:

https://github.com/openstack/nova/commit/9374566d194be1e861e7d08dd0e3b2a615ff408c

It shows up a ton:

http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22Deleting%20stale%20allocation%20for%20instance%5C%22%20AND%20tags%3A%5C%22screen-n-cpu.txt%5C%22&from=7d

It shouldn't be a warning. This is when we're deleting resource provider allocations for instances that are being deleted, it's normal operation as far as I can tell.

Matt Riedemann (mriedem)
Changed in nova:
status: New → Confirmed
importance: Undecided → Medium
Chris Dent (cdent)
Changed in nova:
assignee: nobody → Chris Dent (cdent)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

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

Changed in nova:
status: Confirmed → In Progress
Changed in nova:
assignee: Chris Dent (cdent) → Matt Riedemann (mriedem)
Changed in nova:
assignee: Matt Riedemann (mriedem) → Chris Dent (cdent)
Changed in nova:
assignee: Chris Dent (cdent) → Matt Riedemann (mriedem)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/468519
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=590ecfb894a7da0c9a16ab9a60638963a10e48db
Submitter: Jenkins
Branch: master

commit 590ecfb894a7da0c9a16ab9a60638963a10e48db
Author: Chris Dent <email address hidden>
Date: Fri May 26 19:25:18 2017 +0000

    Changing deleting stale allocations warning to debug

    Deleting the allocations is an expected action, and happens
    frequently so we don't want it to be a warning. It is useful
    as a piece of debug information, however.

    Change-Id: Idf88eef036bbe8deca190366f052ab9e355de6e9
    Closes-Bug: #1693903

Changed in nova:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (stable/ocata)

Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/469628

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/nova 16.0.0.0b2

This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (stable/ocata)

Reviewed: https://review.openstack.org/469628
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9f84d0d4358345c3fd29edb8da2a4d75803c11d6
Submitter: Jenkins
Branch: stable/ocata

commit 9f84d0d4358345c3fd29edb8da2a4d75803c11d6
Author: Chris Dent <email address hidden>
Date: Fri May 26 19:25:18 2017 +0000

    Changing deleting stale allocations warning to debug

    Deleting the allocations is an expected action, and happens
    frequently so we don't want it to be a warning. It is useful
    as a piece of debug information, however.

    Conflicts:
          nova/compute/resource_tracker.py
          nova/tests/unit/compute/test_resource_tracker.py

    NOTE(mriedem): The conflict is due to change
    I80ba844a6e0fcea89f80aa253d57ac73092773ae in Pike where
    this code was all moved to the resource tracker.

    Change-Id: Idf88eef036bbe8deca190366f052ab9e355de6e9
    Closes-Bug: #1693903
    (cherry picked from commit 590ecfb894a7da0c9a16ab9a60638963a10e48db)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/nova 15.0.7

This issue was fixed in the openstack/nova 15.0.7 release.

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.