Discrepancy Between Expected and Observed Behavior in GC Scheduling: Cron Parameter Requirement in Development UI

[goutham1012]

1. In the provided screenshot, when scheduling Garbage Collection (GC) for every hour with one worker, the GC job appears to be correctly scheduled on an hourly basis. However, while testing this feature in the Harbor swagger, we encountered a response indicating that the cron parameter is mandatory. Could someone help on this?

2. In the given input parameters "--schedule_type Weekly" and "--schedule_cron "0 30 5 * * *"", the presence of "--next_scheduled_time "2024-01-06T11:50:21.014Z"" seems contradictory or redundant. Could someone clarify its purpose?.
   
   
   

[MinerYang]

For Q1 => it is designed to be this for now, when using swagger api, cron string is needed, please set as 0 0 * * * *, otherwise, you could choose via UI to edit the GC cron schedule.
For Q2 => the 2024-01-06T11:50:21.014Z is base on the standard UTC time 12:00 am and converted to your own time zone. And please wait for a few seconds to allow the page update the tine

[goutham1012]

@MinerYang
Thanks for your response.
For Q2: - I am asking about how a scheduled cron job interacts with the --next_schedule_time parameter. Specifically, if a cron job is scheduled for 5:30 AM, but i provided a --next_schedule_time of, say, 8:07 AM, which time will the job follow? Is it going to start from the provided --next_schedule_time or from the original cron schedule of 5:30 AM?

I need clarification whether the --next_schedule_time parameter overrides the cron schedule or if the cron job still initiates based on its predefined time despite the --next_schedule_time input.?

[MinerYang]

this next_schedule_time para is not interact with actual schedule API, just a user friendly design to notify you next rough schedule time.

[github-actions]

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

[github-actions]

This issue was closed because it has been stalled for 30 days with no activity. If this issue is still relevant, please re-open a new issue.