[Openstack-operators] Neutron metering agent
george.shuklin at gmail.com
Sun Sep 7 12:06:46 UTC 2014
Yep, it is bug.
I report it, and one guy close in (hate you, devstack), but now it seems
be in the process of fixing. But there is an 25% chance it will be
ported to icehouse and 5% change for havana.
This bug happens if you got more than one network node. If routers are
in database, but not present on network node running metering agent, it
will fail to do anything.
We manage to scramble patch to work with problem, but it is rather
drastic - we skip all errors in that place of code and continue.
If you want I cant post patch, but you gonna need to rebuild neutron
package (rather annoying process).
Here my bugreport:
On 09/07/2014 10:06 AM, Xav Paice wrote:
> A quick query if anyone is using the neutron metering agent to measure
> traffic in/out of routers:
> When adding the metering label and rules, on some, but not all, of our
> routers, I get a traceback in the metering_agent.log pointing at
> "TRACE neutron.openstack.common.rpc.amqp TypeError: cannot concatenate
> 'str' and 'NoneType' objects".
> After that error, the router no longer passes traffic other than ping
> until we stop the metering agent, and restart the L3 agent.
> This doesn't seem to affect routers with only one subnet, and only one
> router in the tenant - but I may be completely misunderstanding the
> whole thing here. It appears as soon as we get a router with more than
> one network (plus gateway) we get trouble.
> We're using Havana on Trusty, and the current Cloud Archive packages.
> The rules are a simple egress and ingress, 0.0.0.0/0, both on the same
> Anyone had similar experiences, or got tips for diagnosing this?
> I will be reading the code over the next few days :)
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
More information about the OpenStack-operators