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

[Rafael Weingartner]

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.

[Rodolfo Alonso (rodolfo-alonso-hernandez)]

Patch: https://review.opendev.org/#/c/751775/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/751775
Committed: https://opendev.org/openstack/neutron/commit/3c0d57c884d574485ac6fb4cad52caec5f220df4
Submitter: Zuul
Branch: master

commit 3c0d57c884d574485ac6fb4cad52caec5f220df4
Author: Rafael Weingärtner <email address hidden>
Date: Mon Sep 14 08:16:04 2020 -0300

    Set metering iptables chain not found LOG level to WARNING

    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. Therefore, we propose here to change the LOG message from error
    to warning.

    Closes-Bug: #1904874
    Change-Id: I1805a07cef7fc7d7b041e582a4d79fb1a805df71

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 18.0.0.0rc1 release candidate.