[kolla] Kolla-ansible plays with --limit failing if a compute host is down.

Albert Braden ozzzo at yahoo.com
Mon Nov 7 13:24:54 UTC 2022


 When I encounter that I edit the inventory and comment out the down host.
     On Friday, November 4, 2022, 05:16:32 PM EDT, Aidan Collins <aidan.collins at twosigma.com> wrote:  
 
  <!--#yiv1189160043 filtered {}#yiv1189160043 filtered {}#yiv1189160043 p.yiv1189160043MsoNormal, #yiv1189160043 li.yiv1189160043MsoNormal, #yiv1189160043 div.yiv1189160043MsoNormal {margin:0in;font-size:11.0pt;font-family:"Calibri", sans-serif;}#yiv1189160043 span.yiv1189160043EmailStyle17 {font-family:"Calibri", sans-serif;color:windowtext;}#yiv1189160043 .yiv1189160043MsoChpDefault {font-family:"Calibri", sans-serif;}#yiv1189160043 filtered {}#yiv1189160043 div.yiv1189160043WordSection1 {}-->
Hello,
 
It seems that the kolla-ansible plays reconfigure, prechecks, bootstrap-servers and deploy all fail when using limit if any compute host is down, even if it is not the one being specified by limit.
 
Is there any way to configure gather-facts in these plays to not fail if this is the case? Due to the size of our plant we sometimes need to take down a compute host for maintenance and still provisiion new ones. We are using Victoria. 
 
  
 
Thanks a lot
 
-aidan
 
  
   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20221107/cea96eae/attachment.htm>


More information about the openstack-discuss mailing list