When a message is provided in system/node reboot command, sometimes the shell command can try interpreting special chars in the message.
e.g.: cli> request system request system reboot message "-msg"

Downloaded junos-evo-install-ptx-x86-64-22.4R2-S1.8-EVO.iso to install on PTX10K8.

Uploaded image, installed successfully via req system software add and 'show system software list' shows 22.4R2-S1 as being installed and the next boot version.

After entering 'request system reboot', the REs did not reboot.

The linecards did reboot, but they are stuck in 'Onlining' after 40 minutes of waiting and cannot reboot because it is already scheduled for over 40 minutes ago.

admin@re0> request system reboot

The entire system (all nodes) will reboot causing traffic loss, do you wish to continue? [yes,no] (no) yes

System is already scheduled to be shutdown

{master} admin@re0> show system reboot reboot of system is scheduled at Fri Aug 11 20:40:40 2023

{master} admin@re0> show system uptime

Current time: 2023-08-11 21:21:16 UTC

Time Source: NTP CLOCK

Node booted: 2023-08-07 07:51:31 UTC (4d 13:29 ago)

System booted: 2023-08-07 07:52:35 UTC (4d 13:28 ago)

Protocols started: 2023-08-07 07:54:42 UTC (4d 13:26 ago)

Last configured: 2023-08-10 17:32:30 UTC (1d 03:48 ago) by admin 9:21PM up 4 days, 13:29, 2 users, load averages: 0.42, 0.43, 0.68

Workaround:
Issue reboot command on the shell (for all RE nodes)


Root-Cause:
When a message is provided in system/node reboot command, sometimes the shell command can try interpreting special chars in the message. Add quotes around message to ensure that shutdown command doesnt try to interpret the message as command options