yahoo-eng-team team mailing list archive

[OpenStack Infra <1571544@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/307039
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b64b0c762bbd41c0ce681aca2ceee05aaea0bdb8
Submitter: Jenkins
Branch:    master

commit b64b0c762bbd41c0ce681aca2ceee05aaea0bdb8
Author: Miguel Angel Ajo <mangelajo@xxxxxxxxxx>
Date:   Mon Apr 18 11:46:13 2016 +0200

    Don't log warning for missing resource_versions
    
    Since mitaka, agents can send a new report about the resource versions
    they know about, and subscribe via rpc callback push mechanisms.
    Some agents don't depend on versioned objects via push, and therefore
    don't need to update neutron-server about such details, anyway server
    side was complaining when that dictionary was missing on the state
    report.
    
    This patch avoids the warning log for missing 'resource_versions'
    field in the agent status report.
    
    Change-Id: Ief5186871515a5700afb56ac5e3fe493b4a05e8e
    Closes-Bug: 1571544


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

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

Title:
  continuous warning in q-svc "Dictionary resource_versions for agent is
  invalid"

Status in neutron:
  Fix Released

Bug description:
  neutron server continuously giving below warnings
  2016-04-18 08:27:41.546 WARNING neutron.db.agents_db [req-49efe7cf-91fa-4a0a-b036-86aac35e09aa None None] Dictionary resource_versions for agent Metadata agent on host vagrant is invalid.
  2016-04-18 08:27:41.546 WARNING neutron.db.agents_db [req-49efe7cf-91fa-4a0a-b036-86aac35e09aa None None] Dictionary resource_versions for agent DHCP agent on host vagrant is invalid.
  2016-04-18 08:27:41.547 WARNING neutron.db.agents_db [req-49efe7cf-91fa-4a0a-b036-86aac35e09aa None None] Dictionary resource_versions for agent L3 agent on host vagrant is invalid.

  It can be reproducible with single node setup on latest upstream
  neutron.

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