Description of problem:
When calling to update hostname of a virtual port the OVN revision number is not bumping. Afterward, in the next trigger, the maintenance task would compare both and run update_port to fix the issue (just the revision number).

Additionally when the update_port called from maintenance task is fixing the revision number of the LSP (OVN NB DB) and corresponding Port_Binding(OVN SB DB), Neutron receives some events from OVN SB DB from Port_Binding table that retrofeed the issue.

This can be easily reproduced doing several updates over one VIP port using openstack cli.

Version-Release number of selected component (if applicable):
16.2.6

How reproducible:
Always

Steps to Reproduce:
1. Create a VIP port and associate to a VM Port, or create a Octavia LB and check its VIP port.
2. Send several openstack port set --description 'changing...' VIP_PORT_UUID
3. Compare the revision number in Neutron DB and LSP on OVN NB DB
4. Maintenance task will be triggered every 5' trying to equal the rev_number for both objects.

Actual results:
Loop trying to fix the revision_number by the maintenance task

Expected results:
Bumping the revision_number accordingly to avoid any unneccesary fix by the maintenance task

Additional info: