yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #43782
[Bug 1528850] Re: log level of respawning event in ProcessMonitor should not be ERROR
Reviewed: https://review.openstack.org/260977
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=2631a495d839254a8d0e22e87e149b063758236d
Submitter: Jenkins
Branch: master
commit 2631a495d839254a8d0e22e87e149b063758236d
Author: zoukeke@xxxxxxxxxxxxxxxxxxxx <zoukeke@xxxxxxxxxxxxxxxxxxxx>
Date: Wed Dec 23 21:15:51 2015 +0800
Change log level from error to warning
The service respawning action of ProcessMonitor is normal handling. So
the log level in external_process.py should not be error.
Closes-Bug: #1528850
Change-Id: Ie335f521b09310a577eb4fb03946dfba484eef61
** 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/1528850
Title:
log level of respawning event in ProcessMonitor should not be ERROR
Status in neutron:
Fix Released
Bug description:
https://github.com/openstack/neutron/blob/master/neutron/agent/linux/external_process.py#L250
I suppose the log level should be info or warning.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1528850/+subscriptions
References