From c5998812276f38ad2ced7d570b6a862bc8411b38 Mon Sep 17 00:00:00 2001 From: Jason Anderson Date: Fri, 11 Oct 2019 16:51:28 -0500 Subject: [PATCH] Update git submodules * Update blazar from branch 'master' - Fix issue moving hosts back to freepool If an aggregate fails to be created for some reason, for example because the requested node is not in the freepool, some cleanup occurs. Part of the cleanup is ensuring the target node is moved _back_ to the freepool. This should theoretically "heal" cases where the node wasn't in the freepool but also wasn't in some lease aggregate. However, this call to Nova's API refers to the freepool aggregate by its name, which is not supported here: the ID must be used[1]. This caused this operation to fail and raise a NotFound, confusingly (because Nova couldn't find an aggregate with ID='freepool' for example.) [1]: https://docs.openstack.org/api-ref/compute/?expanded=add-host-detail#add-host Closes-Bug: #1847821 Change-Id: I7af4d407b183578617131f0de42becb3dc2bc415 --- blazar | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blazar b/blazar index 1dbc30202b..0346b02cce 160000 --- a/blazar +++ b/blazar @@ -1 +1 @@ -Subproject commit 1dbc30202bddfd4f03bdc9a8005de3c363d2ac1d +Subproject commit 0346b02ccea75b992d0b72a6dbaa1f05864450e0