CMD: The schedule created by using create_schedule with <first_time> without icalendar are restarted frequently!

Use this category only if you have build GVM from sources or if you use packages provided by a 3rdparty repository.

Please read About the Greenbone Source Edition (GSE) and About GVM Architecture before posting.

When posting you should provide information about your environment using the following template:

GVM versions

**gsad: 8.0.1 (‘gsad --version’)
**gvmd:8.0.1 (‘gvmd --version’)
**openvas-scanner:6.0.1 (‘openvas --version’, in older GVM versions < 11: ‘openvassd --version’)


Operating system: Linux banel64 #1 SMP Wed Nov 23 13:07:52 UTC 2011 x86_64 x86_64 x86_64 GNU/LinuxKernel: (‘uname -a’)
**Installation method / source: source code

gvm-cli -c ./gvm-tools.conf inet --hostname --port 9390 --xml ‘<create_schedule>schedule_snn_define_5Asia/Hong_Kong<first_time><day_of_month>7</day_of_month>172192020</first_time>1hour</create_schedule>’
<create_schedule_response status=“201” status_text=“OK, resource created” id=“ff7cdf6b-620e-4a8e-b965-92c78ea340b9”></create_schedule_response>

I read gvmd’s log file “gvmd.log” and found the reason,

when call set_task_schedule_next_time (
** task_schedule_iterator_task (&schedules),**
** icalendar_next_time_from_string (icalendar, zone, 0));**, the time return by icalendar_next_time_from_string (icalendar, zone, 0) all be same, 1599470460.

Could you please open a new issue at Issues · greenbone/gvmd · GitHub so that the development team could have a look at this?