As reported in the community forum [0], the resource relocation endpoint would produce a warning: > Can't use an undefined value as an ARRAY reference
In the get_resource_motion_info() function, properly initialize the array references in the $blocking_resources_by_node hash to avoid this. Note that the migration endpoint needs to be adapted to only include 'blocking-resources' in the result if there is at least one entry in the array to be compatible with this change. Align the behavior of both migration and relocation endpoints, so that the migration endpoint correctly handles the initialized, but empty array too. Alternatively, it could've been done the other way with the relocation endpoint also checking for the array reference to be undefined if no entries are to be added to the array, but since $comigrated_resources is also initialized when empty, it seemed cleaner to go with the approach here. [0]: https://forum.proxmox.com/threads/173149/ pve-ha-manager: Fiona Ebner (1): api: relocate/migrate resource: improve initialization of variables to avoid Perl warning src/PVE/API2/HA/Resources.pm | 2 +- src/PVE/HA/Config.pm | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) Summary over all repositories: 2 files changed, 2 insertions(+), 1 deletions(-) -- Generated by git-murpp 0.5.0 _______________________________________________ pve-devel mailing list [email protected] https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
