Page MenuHomeVyOS Platform

reboot in <x> not working as expected
Closed, ResolvedPublicBUG

Description

[email protected]:~$ date
Wed 29 Dec 2021 12:30:22 PM CET
[email protected]:~$ reboot in 
Possible completions:
  <Minutes>     Reboot in X minutes

      
[email protected]:~$ reboot in 300
Invalid time "300". The valid format is HH:MM
[email protected]:~$ reboot in 5:0
Shutting down at Thu 2021-12-30 05:00:00 CET (reboot)...
[email protected]:~$ reboot in 05:00
Shutting down at Thu 2021-12-30 05:00:00 CET (reboot)...
[email protected]:~$ reboot at 
Possible completions:
  <HH:MM>       Reboot at a specific time

      
[email protected]:~$ reboot at 18:30
Shutting down at Wed 2021-12-29 18:30:00 CET (reboot)...
[email protected]:~$ show reboot 
Shutting down at Wed 2021-12-29 18:30:00 CET (reboot)...

reboot in tab completion is wrong, and reboot in doesnt work as expected. it seems to do the same thing as reboot at

tested in 1.2.8 and 1.3.0

Details

Difficulty level
Unknown (require assessment)
Version
1.3.0 and 1.2.8
Why the issue appeared?
Will be filled on close
Is it a breaking change?
Unspecified (possibly destroys the router)
Issue type
Unspecified (please specify)

Event Timeline

The error is received when the input for minutes is provided in three digits.

[email protected]:~$ reboot in 99

Broadcast message from [email protected] (somewhere) (Wed Dec 29 19:30:13 2021):

System reboot is scheduled 99

Reboot is scheduled 2021-12-29 21:09:13
[email protected]:~$ reboot in 100
Invalid time "100". The valid format is HH:MM
SrividyaA added a project: VyOS 1.4 Sagitta.
SrividyaA added a subscriber: SrividyaA.

I ve tested this scenario on VyOS 1.4-rolling-202201200814, as said Srividya you can choose minutes betwen 1-99.
If this is critical, you can expand the range by opening a "feature request".

This comment was removed by n.fort.

We didn't receive the customer's request.
The timers work without problems.
I'll open a design request to see the range 1-99.

Viacheslav added a subscriber: Viacheslav.

Issue not resolved, re-open

Viacheslav changed the task status from Open to Confirmed.Feb 8 2022, 6:08 PM