MaxScale 24.02.6 GUI does not reflect parameter changes from Configuration Synchronization

MaxScale 24.02.6 GUI does not reflect parameter changes from Configuration Synchronization. If you make changes using the MaxScale GUI or maxctrl on MaxScale node 1, the MaxScale GUI on MaxScale node 2 does not reflect the changes. The maxctrl output is correct for MaxScale node 2. This behavior is not seen in MaxScale 25.01.2, it behaves as expected.

Steps to reproduce

• Set up 2 MaxScales, with identical base MaxScale configuration that has a monitor for a database
• Set up Configuration Synchronization by putting the following values in the globals section of the MaxScale configuration file. Replace with the appropriate values for your setup

  [maxscale]

  # ... other global settings

  config_sync_cluster = my_maxscale_cluster

  config_sync_db = maxscale_config_db

  config_sync_user = maxscale_sync

  config_sync_password = your_strong_password

• Restart both MaxScale nodes
• Using either the MaxScale GUI or maxctrl on MaxScale node 1 set the monitoring_interval of the monitor to a new value
• Viewing the monitor parameters on MaxScale node 1 shows the correct value
• Viewing the monitor parameters on MaxScale node 2 shows the wrong value
• Running the following on MaxScale node 2 shows the correct value

  maxctrl show monitor GaleraMonitor | grep 'monitor_interval'

• There are two ways I have discovered so far to make the MaxScale GUI reflect the correct value. First is to restart the MaxScale service. The second way is to make an identical change to the monitoring_interval of the monitor. This updates the GUI, but has not effect because no real change was made.

See the attached files. I made a change to the monitor on node 1 via maxctrl and it is reflected on the node 1 GUI screenshot. However, you only see the new value on node 2 via the maxctrl command and not on the GUI.