I got it, The plugin creates a logical entry for the port which is stored in the database. The agent is responsible for only checking changes in the ovs bridge and updating those changes and the database.

It works like this..

Other services (e.g. Nova, neutron l3 router, etc) create the actual port on the integration bridge.

The agent looks for any changes in the ovsdb for the bridge by using ovsdb-client in a pooling loop.

If it finds a new entry, it gets the port details from ovsbd as well as the plugin via RPC and checks for the port binding attributes.

If the attributes are found and the ofport entry in the ovsdb for the port is valid, it sets the port's tag allotted to the port's network via ovs-vsclt and updates the port status to ACTIVE via RPC to plugin.

In my implementation, I forgot to bind my port correctly, hence the status of the port was not updated to ACTIVE.