Bug #2771
oneflow recover failed
Status: | Closed | Start date: | 03/06/2014 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | Carlos Martín | % Done: | 0% | |
Category: | OneFlow | |||
Target version: | Release 4.6 | |||
Resolution: | fixed | Pull request: | ||
Affected Versions: | OpenNebula 4.4 |
Description
Hello,
After a failed scaling with oneFlow, I got an error on console/web application (as seen in oneflow-recover-output.html).
After digging in the code, I think the error may be avoid using this patch (not sure that nodes_dispose should be used instead on n_dispose).
--- /usr/lib/one/oneflow/lib/models/role.rb 2014-03-06 14:02:08.723267984 +0100 +++ /usr/lib/one/oneflow/lib/models/role.rb.orig 2014-03-06 14:01:51.136955843 +0100 @@ -795,7 +795,7 @@ shutdown_nodes(nodes_dispose, true) - set_cardinality( get_nodes.size() - nodes_dispose.size() ) + set_cardinality( get_nodes.size() - n_dispose.size() ) end # Deletes VMs in DONE or FAILED, and sends a boot action to VMs in UNKNOWN
Regards,
Nicolas
Associated revisions
Bug #2771: Fix oneflow recover after a failed scaling
Bug #2771: Fix oneflow recover after a failed scaling
(cherry picked from commit f5d1b9aac7253fcd0e1e92e9bc3b9df7d7bfb0cf)
History
#1 Updated by Nicolas Belan over 7 years ago
EDIT: patch -R, inverted file names ... sorry
#2 Updated by Ruben S. Montero over 7 years ago
- Assignee set to Carlos Martín
- Target version set to Release 4.6
#3 Updated by Ruben S. Montero over 7 years ago
- Status changed from Pending to New
#4 Updated by Carlos Martín over 7 years ago
- Status changed from New to Closed
- Resolution set to fixed
Patch applied, thank you!