On MX304 device and LC9600 line card, upon Routing Engine switchover chassisd on new master was not re-initializing the tunnel/inline services configuration data, hence all static tunnel interface (GRE, IP-IP, Multicast (MT), PIM, Logical tunnels and Virtual loopback tunneling (VT)) and inline interfaces will get bounced (deleted and re-created) after doing any CLI commit after an RE switchover. There will be momentary impact on traffic using these interfaces.

MX10008 gr- or lt- etc interfaces would flap after RE switchover and commit

<< switchover from RE1 to RE0
{master}
root@router> request chassis routing-engine master switch 
Jun 15 13:01:56
Toggle mastership between routing engines ? [yes,no] (no) yes 
Jun 15 13:01:57

Resolving mastership...
Complete. The other routing engine becomes the master.

<< do commit full on RE0
{master}[edit]
root@router# run show interfaces lt-0/0/0    
Jun 15 13:03:42
Physical interface: lt-0/0/0, Enabled, Physical link is Up
  Interface index: 437, SNMP ifIndex: 717
  Type: Logical-tunnel, Link-level type: Logical-tunnel, MTU: Unlimited, Speed: 1000 Mbps
  Device flags   : Present Running
  Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
  Link flags     : None
  Physical info  : 13
  Current address: e6:23:3c:ee:57:d3, Hardware address: e6:23:3c:ee:57:d3
  Last flapped   : 2023-06-15 12:41:41 IST (00:22:01 ago)  <<<
  Input rate     : 0 bps (0 pps)
  Output rate    : 0 bps (0 pps)

root@router# commit full     
Jun 15 13:03:48
re0: 
configuration check succeeds
re1: 
commit complete
re0: 
commit complete

<< interface flapped and index changed 
{master}[edit]
root@router# run show interfaces lt-0/0/0 
Jun 15 13:04:13
Physical interface: lt-0/0/0, Enabled, Physical link is Up
  Interface index: 653, SNMP ifIndex: 717
  Type: Logical-tunnel, Link-level type: Logical-tunnel, MTU: Unlimited, Speed: 1000 Mbps
  Device flags   : Present Running
  Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
  Link flags     : None
  Physical info  : 13
  Current address: e6:23:3c:ee:57:d3, Hardware address: e6:23:3c:ee:57:d3
  Last flapped   : 2023-06-15 13:03:59 IST (00:00:14 ago)  <<<
  Input rate     : 0 bps (0 pps)
  Output rate    : 0 bps (0 pps)

The problem has been fixed in PR1742510 and resolved in following vesions , there is no workaround:

evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:21.4R3-S5-J6 junos:21.4R3-S6 junos:22.2R3-S3 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1 junos:23.4R1