Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
...
This is generally a different symptom of the same problem as above (flows stuck in PENDING_ADD). If ONOS can’t match the returned flow stats with flow rules in the store, it will remove what it considers to be an extraneous flow and install the flow in the store again. The solution to this problem is to ensure that ONOS can match observed flows with its internal flow store.
Why do I see extra hosts in the CLI or GUI?
ONOS' dynamic host discovery works by observing packets sent by hosts on the dataplane that come up to the controller (e.g. OpenFlow devices send packets to the controller by using packet-ins). It looks at the source MAC address of the packets and creates host entries for these MAC addresses. In some situations, packets may be observed by ONOS that are not sent by real hosts in the network. In particular, when using Mininet to emulate a network, sometimes extra hosts will be observed apart from the real hosts in the Mininet network. This is simply an artifact of the way Mininet uses Linux to create networks - it is creating interfaces in Linux which the OS is sending packets out of, and these packets are observed by ONOS and appear as hosts. It is usually safe to simply ignore the extra hosts.
Where can I find the ONOS log?
...