Warnings in the Odenos log

[aekom87]

Hi,

My name is Andrey Komarov, and I am taking part in a development of an Odenos-based SDN controller.

In our controller we are using the Federator component, and we have faced somewhat of an issue when we tried to delete a flow from a federeated network. The flow has been deleted successfully from both original networks, however in Odenos logs we see the following worning:

2015-08-31 08:07:57 WARN NetworkInterface:1293 - invalid GET(404) to federated-nw: 'flows/1' "flow_id not found"

We added a call stack print right before the line NetworkInterface:1293 and got the following result:

2015-08-31 08:07:57 ERROR NetworkInterface:1292 - [java.lang.Thread.getStackTrace(Thread.java:1552), org.o3project.odenos.core.component.NetworkInterface.getObjectToNetwork(NetworkInterface.java:1292), org.o3project.odenos.core.component.NetworkInterface.getFlow(NetworkInterface.java:696), org.o3project.odenos.core.component.Logic.deleteConversion(Logic.java:1638), org.o3project.odenos.component.federator.Federator.onFlowDelete(Federator.java:894), org.o3project.odenos.core.component.Logic.onFlowChanged(Logic.java:578), org.o3project.odenos.core.component.Logic.onEvent(Logic.java:417), org.o3project.odenos.remoteobject.RemoteObject.doPostEvent(RemoteObject.java:422), org.o3project.odenos.remoteobject.RemoteObject.dispatchEvent(RemoteObject.java:295), org.o3project.odenos.remoteobject.actor.Actor$1.run(Actor.java:181), java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142), java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617), java.lang.Thread.run(Thread.java:745)]

So it looks like after the FLOW_CHANGED.DELETED event arrived to the Federator from the Federated network, Federator tried to request flow data from the Federator netowork. However, the flow has been already deleted from the Federated network. Therefore the 404 response was received by Federator and the warning was logged.

The warning does not seem to lead to any actual problem, however it confuses us a bit.

Could you please have a look at this?

Thanks in advance,
Andrey

[haizawa]

We could not reproduce this phenomenon.
Can you get a log in the log level "DEBUG"?