-
### What is the problem you are trying to solve with this feature?
Reoccurring Maintenance activates are automatically created on completion.
### What is the solution you are proposing?
When creat…
-
### Feature Request / Improvement
Current implementation of maintenance operations scheduling provides several options:
- commit count
- data file count
- data file size
- positional delete file …
-
### What would you like to be added?
#### Background
Some scheduling plugins (especially out-of-tree plugins) maintain additional information through `EventHandler`.
For non-Pods types, this …
-
### ⚠️ Please verify that this question has NOT been raised before.
- [X] I checked and didn't find similar issue
### 🛡️ Security Policy
- [X] I agree to have read this project [Security Poli…
-
TestNodesMaintenance::test_node_maintenance_restart_activate[worker] is failing on power
The worker node in the test reaches not ready, scheduling disabled but still assertion fails.
Also it's not …
-
### Is the feature request related to a problem? Please describe.
I'm admin of two >200 user nodes. So I need to send ~400 mails in case of maintenance windows.
Furthermore, it's not that reliable…
-
**Describe the bug**
As part of the requirements for issue: https://github.com/harvester/harvester/issues/4888 we introduced additional logic to identify VM's which cannot be scheduled to other n…
-
## Summary
Task scheduling framework able to support data retention policies and execute scheduled tasks, such as backup, log maintenance etc.
## Expected outcome
A SQL syntax to define data …
-
The start time always shows one hour ahead of the current time , this is ok as pre populated but majority of the times colleagues overlook that thing while scheduling maintenance window and schedule t…
-
My stderr output is flooded with lines starting `NOTICE:`, `FATAL:`, etc. e.g.
```
NOTICE: next maintenance_task ID 364
NOTICE: scheduling execution of 364 maintenance_task
NOTICE: next maint…
gajus updated
4 years ago