Forbid running an on-demand backup if another backup is already running

Tested with Everest v1.1.0-rc1 version.

In mongodb, the UI now displays an error message if an on-demand is started, when a scheduled backup is running or just starts

At a certain point, I was able to get the below, but in the backend the scheduled backup had already completed and its status was not updated in the UI, so there is a time gap between the backend and UI

Hence closing this issue. Thanks Mayank for fixing this issue.

@Manish Chawla The fix has been created and is a part of 1.1.0.

Ok, I see the problem now.

The statuses for mongodb backups are actually a bit different from the other two. If the status is ""or "waiting", it isn’t really considered as running by Everest.

Moreover, Everest server looks at the dbbackup object, not psmdb-backup. And everest-operator does not create a dbbackup object unless psmdb-backup has progressed beyond waiting (due to a known limitation).

I’ll have to think of a temporary workaround for this..

I am attaching a short video, that might help

After the scheduled backup gets created and we can see it in kubernetes (kubectl get psmdb-backup), immediately start a manual backup. I think the scheduled backup does not have a status, when the manual backup is triggered. Then both backups get started and can be seen in the UI. This is happening for mongodb.