bug: Schedule Scan does not run after creating a new schedule scan task

[S3ntago]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Hi,

I found that the schedule scan is not working proberl, after creating a new schedule scan, the scan does not run at all, here an example of creating 2 schedule scans and after 24 hrs they still didn't start.

Expected Behavior

Steps To Reproduce

Create a new schedule scan

Environment

- reNgine: 2.0
- OS: 
- Python: 
- Docker Engine: 
- Docker Compose: 
- Browser:

Anything else?

No response

[github-actions]

👋 Hi @S3ntago,
Issues is only for reporting a bug/feature request. Please read documentation before raising an issue https://rengine.wiki
For very limited support, questions, and discussions, please join reNgine Discord channel: https://discord.gg/azv6fzhNCE
Please include all the requested and relevant information when opening a bug report. Improper reports will be closed without any response.

[NadgobKhan]

Hello, adding more info regarding this issue. I am running on reNgine v2.0.2.
I noticed whenever the scheduled scan is supposed to start, I get this warning in the logs:

rengine-celery-beat-1  | py.warnings | /usr/local/lib/python3.10/dist-packages/django/db/models/fields/__init__.py:1416: RuntimeWarning: DateTimeField PeriodicTask.last_run_at received a naive datetime (2024-02-02 14:58:32.302885) while time zone support is active.
rengine-celery-beat-1  |   warnings.warn("DateTimeField %s received a naive datetime (%s)"
rengine-celery-beat-1  |

So it might have something to do with the way the date of the last_run_at is sent.

[yogeshojha]

Hi @S3ntago thank you for reporting

This will be fixed with #1313 1313