From aggregation device (AD), if satellite image upgrade is pushed to the aggregated satellite device (SD) groups via command “request system software add /var/tmp/satellite-22.4R3.25-signed.tgz upgrade-group <group_name>”
The session will be terminated with “session failure” error message and "mgd.core" will be generated. This will be occurring every time the upgrade command is executed from AD to any SD group
Session termination and mgd core will be generated
As an example, MX is configured as AD and QFX has SD, Attempting an upgrade from AD to a connected QFX SD group 2
root@AD-mx> request system software add /var/tmp/satellite-22.4R3.25-signed.tgz upgrade-group qfx-group2
error: session failure: unexpected termination
error: remote side unexpectedly closed connection
root@AD-MX:/var/tmp # cli
{master}
root@AD-MX> show system core-dumps
/var/crash/*core*: No such file or directory
-rw------- 1 root wheel 7588028 Mar 28 20:08 /var/tmp/mgd.core.0.gz >>>>>>>> core-dump is seen
/var/tmp/pics/*core*: No such file or directory
/var/crash/kernel.*: No such file or directory
/var/jails/rest-api/tmp/*core*: No such file or directory
/tftpboot/corefiles/*core*: No such file or directory
total files: 1
Attempting upgrade again to another connected QFX SD group 1
root@AD-MX> request system software add /var/tmp/satellite-22.4R3.25-signed.tgz upgrade-group qfx-group1
root@AD-MX:~ # cli
-rw------- 1 root wheel 7588028 Mar 28 20:08 /var/tmp/mgd.core.0.gz
-rw------- 1 root wheel 7590178 Mar 29 09:36 /var/tmp/mgd.core.1.gz >>>>>>> another mgd core generated
total files: 2
PR1799277 is opened to address this issue
The satellite package is not conforming to the expected junos version format leading to the problem reported.
The code which parses this version string has been modified to handle such format incompatibility gracefully.
Fix has been identified and is resolved in evo:23.4R2-EVO evo:24.2R1-EVO evo:24.3R1-EVO junos:22.4R3-S2 junos:23.4R2 junos:24.2R1 junos:24.3R1