yahoo-eng-team team mailing list archive

[Rafael Weingartner <1904874@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When routers are migrated from one Neutron agent to the other, the
metering IPtables rules are removed, which can cause some exceptions
that can be ignored. The metering agent already handled this situation.
However, it logs the message as an ERROR, which can triggers alarms in
the cloud monitoring systems.

The message is imported to be logged. However, we should change it to
warning, instead of error. Normally, in complex cloud environments,
people configure alarms to be triggered whenever an error message
appears, and operators have to act upon it. These messages can trigger
such situations, which are misleading. Therefore, we propose here to
change the LOG message from error to warning.

** Affects: neutron
     Importance: Undecided
         Status: New

** Description changed:

- When routers are migrated from one Neutron agent to the other, the metering IPtables
- rules are removed, which can cause some exceptions that can be ignored. The metering
- agent already handled this situation. However, it logs the message as an ERROR, which
- can triggers alarms in the cloud monitoring systems.
+ When routers are migrated from one Neutron agent to the other, the
+ metering IPtables rules are removed, which can cause some exceptions
+ that can be ignored. The metering agent already handled this situation.
+ However, it logs the message as an ERROR, which can triggers alarms in
+ the cloud monitoring systems.
  
- The message is imported to be logged. However, we should change it to warning, instead
- of error. Normally, in complex cloud environments, people configure alarms to be triggered
- whenever an error message appears, and operators have to act upon it. These messages can trigger
- such situations, which are misleading. Therefore, we propose here to change the LOG message from error to warning.
+ The message is imported to be logged. However, we should change it to
+ warning, instead of error. Normally, in complex cloud environments,
+ people configure alarms to be triggered whenever an error message
+ appears, and operators have to act upon it. These messages can trigger
+ such situations, which are misleading. Therefore, we propose here to
+ change the LOG message from error to warning.

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

Title:
  Neutron metering iptables chain not found message is logged is ERROR
  level

Status in neutron:
  New

Bug description:
  When routers are migrated from one Neutron agent to the other, the
  metering IPtables rules are removed, which can cause some exceptions
  that can be ignored. The metering agent already handled this
  situation. However, it logs the message as an ERROR, which can
  triggers alarms in the cloud monitoring systems.

  The message is imported to be logged. However, we should change it to
  warning, instead of error. Normally, in complex cloud environments,
  people configure alarms to be triggered whenever an error message
  appears, and operators have to act upon it. These messages can trigger
  such situations, which are misleading. Therefore, we propose here to
  change the LOG message from error to warning.

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