Closed Franco-Sparrow closed 6 months ago
It is an obvious typo. Usually it is not recommended but as it is a string I'd try fixing it in the binary until it is fixed upstream ;-).
cp /usr/bin/oned /usr/bin/oned-$(date +%s)
sed -i.bak 's|PARALELL|PARALLEL|' /usr/bin/oned
Checking what was changed in the bynary:
diff <(xxd /usr/bin/oned.bak) <(xxd /usr/bin/oned)
265232c265232
< 0040c0f0: 4c45 4c4c 0042 4143 4b49 4e47 5f55 505f LELL.BACKING_UP_
---
> 0040c0f0: 4c4c 454c 0042 4143 4b49 4e47 5f55 505f LLEL.BACKING_UP_
Let's try the new binary
systemctl restart opennebula
Hope this helps.
Best Regards, Anton
@atodorov-storpool Thanks Sir, this solved the issue :)
The typo is in the line that is referenced:
I have compiled the packages with this fix and work perfectly.
Description
Hi team and @rsmontero.
I testing the new backupjob feature (using rsync driver) and I like this new way to schedule backups, as longs as it allow multiple backups at the same time, following the global configuration in the
/etc/one/sched.conf
. The problem is that Sunstone does not give you the option to create a new job with execution modePARALLEL
(Backups are executed in parallel subject to the available slots). Tried to modify the execution mode attribute, but it always return toSEQUENTIAL
mode. I did this from Sunstone and from CLI, once created the backupjob from Sunstone, it creates the job with execution modeSEQUENTIAL
by default and cant be changed.To Reproduce
Using CLI
Create a file with the backupjob configuration:
Create the backupjob using the previous file:
In this case, the output was as follow:
Check the backupjob details:
The output was as follow, and you can see that execution mode is still
SEQUENTIAL
:Using Sunstone
These pictures follow the creation of the new backupjob and the edition of the attribute
EXECUTION
. Same result as CLI way.Expected behavior
A new backupjob created with the chance to change the execution mode from
SEQUENTIAL
toPARALLEL
for rsync backups.Details
Additional context Add any other context about the problem here.
Progress Status