xcvrd exercises non-host_tx_ready change in value event from state-DB port-table

[jaganbal-a]

Below is the snippet where xcvrd process the event without host_tx_ready in the state-DB port table. Full log is in the attachment "xcvrd_non_tx_ready_event_processing"

May 26 20:17:37.886250 sonic NOTICE pmon#xcvrd[32]: CMIS: Ethernet248 Forcing Tx laser OFF

May 26 20:17:37.904964 sonic WARNING pmon#xcvrd[32]: $$$ Ethernet248 handle_port_update_event() : op=SET DB:STATE_DB Table:PORT_TABLE fvp {'state': 'ok', 'netdev_oper_status': 'down', 'admin_status': 'up', 'mtu': '9100', 'supported_speeds': '', 'supported_fecs': 'rs', 'host_tx_ready': 'true'}
May 26 20:17:37.905200 sonic WARNING pmon#xcvrd[32]: *** Ethernet248STATE_DBPORT_TABLE handle_port_update_event() fvp {'host_tx_ready': 'true', 'index': '-1', 'key': 'Ethernet248', 'asic_id': 2, 'op': 'SET'}
<<<<<<<<<<<<<<<<<<<<<<<
May 26 20:17:37.942950 sonic NOTICE pmon#xcvrd[32]: CMIS: Ethernet248: 400G, lanemask=0xff, state=INSERTED, appl 1 host_lane_count 8 retries=0
May 26 20:17:38.008109 sonic NOTICE pmon#xcvrd[32]: CMIS: Ethernet248: Setting appl=1
May 26 20:17:38.070372 sonic NOTICE pmon#xcvrd[32]: CMIS: Ethernet248: Setting lanemask=0xff

[jaganbal-a]

xcvrd_non_host_tx_ready_event_processing.txt