I did a quick test in my environment and continuous audits works in both *master* and *stable/2024.2 *branches. I was also using the dashboard from *master *branch for both tests. I created Audits using an audit template as shared, with *dummy with scorer *strategy. The audit went to the ONGOING state right away, and proposed an action plan. @Mohd you may want to check the details of your Audits to get more info about Created Date and Next Run Time (the later may be only available using the python-watcherclient) For reference in my env: watcher stable/2024.2: 56dae607 (HEAD -> stable/2024.2, origin/stable/2024.2) [stable-only] Consolidate and improve Zuul CI job definitions watcher master: 1d32e734 (HEAD -> master, origin/master, origin/HEAD) Retry calls to nova API when connection errors are detected watcher-dashboard master: aaebb77 (HEAD -> master, origin/master, origin/HEAD) Merge "Adopt Ruff for security; remove Bandit and fix style" Att, On Tue, Dec 30, 2025 at 1:24 PM Sean Mooney <smooney@redhat.com> wrote:
adding `[watcher]` tag to subject
im on pto for another 2 weeks or so but ill highlight it to others.
2023.1 is EOL but if you report a bug we can see if it reproduces on master and fix it on the supported stable branches if viable.
we have fixed quite a few bugs in the 2025.1 and 2025.2 release that may have been related.
On 30/12/2025 06:45, Mohd Atif Ansari wrote:
Hello OpenStack Community,
I am facing an issue with *Continuous Audits* in Watcher. After creating the audit with an interval, the audit remains in the *PENDING* state and does not generate any action plans.
All Watcher services are running, and the *audit is created successfully without errors*.
Could you please help identify what might be missing or misconfigured?
Openstack version: 2023.1
/*I have attached some screenshots for your reference. */
Thanks, *Mohd Atif Ansari*
------------------------------------------------------------------------ *Disclaimer :*/ The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender.// /
/// /
/E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."// /
-- Douglas Viroel - dviroel