Open Stack

Hi, Rodrigo Lima：

       Have you found the failure notification in the masakari  dashboard or DB( Table notifications)?  If so, the failure notification would trigger the recovery workflow, and you need to check the masakari-api and masakari-engine log to find the detail. If not, it could be a deployment problem, and you need to check the connectivity between masakari-api and masakari-hostmonitor.

 

 

发件人: Rodrigo Lima [mailto:rodrigo.lima at o2sistemas.com] 
发送时间: 2021年12月4日 2:56
收件人: openstack-discuss at lists.openstack.org
主题: [lists.openstack.org代发][kolla-ansible] Default masakari configuration should evacuate instances across nodes in wallaby?

 

I'm working on upgrading an openstack farm from victoria to wallaby. After successful upgrade, I would like to enable hacluster and masakari to test HA between failing compute nodes. Everything seems to be running (pacemaker with the remote nodes OK, corosync without errors, masakari-monitors detects the 2 compute nodes online), but... when I simulate the failure of a node with shutdown, the failure and notification appears in the hostmonitor log, but the instances that were on the failed node don't evacuate, and I couldn't find documentation that explains how to do this specific configuration, if necessary. Does anyone have any ideas?




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20211205/ebd14658/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ~WRD000.jpg
Type: image/jpeg
Size: 823 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20211205/ebd14658/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3606 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20211205/ebd14658/attachment.bin>