Bug 1711390 - Scheduler is dumping all instances on a compute host
Summary: Scheduler is dumping all instances on a compute host
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 10.0 (Newton)
Hardware: x86_64
OS: Linux
low
low
Target Milestone: async
: 10.0 (Newton)
Assignee: Stephen Finucane
QA Contact: OSP DFG:Compute
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-17 16:46 UTC by Stephen Finucane
Modified: 2023-03-21 19:16 UTC (History)
8 users (show)

Fixed In Version: openstack-nova-14.1.0-51.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-03 16:36:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1790126 0 None None None 2019-05-17 16:47:02 UTC
Red Hat Issue Tracker OSP-17468 0 None None None 2022-07-09 14:23:39 UTC
Red Hat Product Errata RHSA-2019:2631 0 None None None 2019-09-03 16:36:50 UTC

Description Stephen Finucane 2019-05-17 16:46:50 UTC
Description of problem:
There is a log message in the scheduler which dumps all instances running on a compute host:


LOG.debug("Update host state with instances: %s", inst_dict)

There are at least 2 problems with this:
  1. it generates huge amount of logs which are not really useful
  2. it crashes when there is an instance with non-ascii name

We don't need to log these are shouldn't

Version-Release number of selected component (if applicable):

OSP 10

How reproducible:

Always

Steps to Reproduce:

Run nova-scheduler.

Actual results:

We see lot of blobs logged.

Expected results:

We should only see the instance UUIDs or some other identifier.

Additional info:

Comment 11 errata-xmlrpc 2019-09-03 16:36:34 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:2631


Note You need to log in before you can comment on or make changes to this bug.