During the onboarding process you might notice, that the SSR is stuck in the "connected" state for a long time under Conductor > Authority > Routers.Verify the error from /var/log/salt/minion
Error: Unable to find a match: 128T-mist-wan-assurance-3.7.6-205; ran because expected version '3.7.6-205' != received version '3.3.1-205' 2024-08-29 08:49:22,287 [salt.loaded.ext.module.async_state:274 ][ERROR ][21781] T128 environment errors: { "Install installer repo RPM": "Command \"dnf install -y https://yum.128technology.com/installer/repo.rpm\" run" 2024-08-29 08:49:22,289 [salt.loaded.ext.module.async_state:286 ][ERROR ][21781] Plugins environment errors: { "Install Mist WAN Assurance": "Error occurred installing package(s). Additional info follows:\n\nerrors:\n - Running scope as unit run-23117.scope.\n Failed to synchronize cache for repo '128t-authenticated-release', disabling.\n Failed to synchronize cache for repo '128t-authenticated-app-data-release', disabling.\n Failed to synchronize cache for repo '128t-authenticated-plugins-release', disabling.\n Failed to synchronize cache for repo '128t-authenticated-release-deps-centos-7-5', disabling.\n Failed to synchronize cache for repo '128t-authenticated-legacy-release', disabling.\n Failed to synchronize cache for repo '128tech-release', disabling.\n Last metadata expiration check: 0:00:00 ago on Thu Aug 29 08:49:18 2024.\n No match for argument: 128T-mist-wan-assurance-3.7.6-205\n Error: Unable to find a match: 128T-mist-wan-assurance-3.7.6-205; ran because expected version '3.7.6-205' != received version '3.3.1-205'"
Verify the rpm version between the conductor and the router, it must be the same.
[root@bei4-sdwan01 salt]# rpm -qa | grep mist 128T-mist-agent-3.1.2643-1.el7.x86_64 128T-mist-wan-assurance-3.3.1-205.x86_64