-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed
Milestone
Description
problem
Once you like to disable an existing schedule for a VM you'll receive an error "Start date [2025-07-10T09:38:45Z[UTC]] can't be before current time". As workaround you just clear the start date and continue.
Once you open the schedule again the old start date will appear.
Same behaviour for enabling a schedule - which is fine for enable.
Once schedule got enabled again the old start date will get used and not the current time like at the moment when I first created the schedule. (Might be okay to keep the original one.)
versions
4.20.1.0
The steps to reproduce the bug
- select a VM
- create a schedule - no changes needed on the form, just click "ok"
- wait 2 minutes to have the start time older than the current time
- open the schedule and disable the schedule - click "ok"
- error message will appear
- clear the start date and click "ok" again - now it will work
...
What to do about it?
I my opinion changing the start date should not be needed once you just want to disable the schedule. It will become effective right away, right?
Metadata
Metadata
Assignees
Labels
No labels