yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1460491@xxxxxxxxxxxxxxxxxx>]

[Expired for neutron because there has been no activity for 60 days.]

** Changed in: neutron
       Status: Incomplete => Expired

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

Title:
  some neutron log should raise up their log level to error

Status in neutron:
  Expired

Bug description:
  neutron logs like:
  https://github.com/openstack/neutron/blob/e933891462408435c580ad42ff737f8bff428fbc/neutron/plugins/ml2/drivers/mech_agent.py#L76
  https://github.com/openstack/neutron/blob/e933891462408435c580ad42ff737f8bff428fbc/neutron/plugins/ml2/drivers/mech_agent.py#L187
  https://github.com/openstack/neutron/blob/e933891462408435c580ad42ff737f8bff428fbc/neutron/plugins/ml2/drivers/mech_agent.py#L200

  they are in warning level or debug level. It may make sense to neutron, but to openstack basic feature, booting instances, warning or debug level seems not so helpful.
  The above log messages will raise when in case booting instances failed, and at the same time, we can find some error level log in nova compute log like, virt_binding error. That error message tells us that we need check neutron, but in neutron log, warning or debug level message doesn't help us to do a quick issue locating.

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