View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001302 | bareos-core | vmware plugin | public | 2021-01-11 16:34 | 2023-08-22 15:29 |
Reporter | fapg | Assigned To | bruno-at-bareos | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Platform | Linux | OS | CentOS | OS Version | 7 |
Product Version | 20.0.0 | ||||
Summary | 0001302: Problem in ovirt-plugin | ||||
Description | In bareos 20, the ovirt plugin fails when running more than one job at once. When finishing one image backup job, bareos stops all images jobs and worst, put information of one job into other! This bug is very bad! and It's a huge regression. Best Regards, Fernando Gomes | ||||
Tags | No tags attached. | ||||
As seen in support RedHat already announced last year the EOL of their product RedHat Virtualization (mid 2024). They also drop a lot of contribution in ovirt. This puts the project in a delicate situation (also moving from CentOS to something else). The crash you are experiencing is probably related to Python module single phase initialization. We finally tracked this down to pycurl being the problem, not necessarily the oVirt XML module. It's sufficient to simply add import pycurl to any Python plugin without even using it to reproduce the segfault. Multi-phase initialization is defined in PEP 489, see also this article https://vstinner.github.io/isolate-subinterpreters.html Bareos will not itself invest effort to either fix upstream pycurl nor ovirt component. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2021-01-11 16:34 | fapg | New Issue | |
2023-08-22 15:29 | bruno-at-bareos | Assigned To | => bruno-at-bareos |
2023-08-22 15:29 | bruno-at-bareos | Status | new => closed |
2023-08-22 15:29 | bruno-at-bareos | Resolution | open => fixed |
2023-08-22 15:29 | bruno-at-bareos | Note Added: 0005333 |