Hi Yipei, That error means the controller worker process was not able to reach the amphora REST API.
I am guessing this is the issue with diskimage-builder which we have patches up for, but not all of them have merged yet [1][2]. Try running my script: https://gist.github.com/michjohn/a7cd582fc19e0b4bc894eea6249829f9 to rebuild the image and boot another amphora. Also, could you provide a link to the docs you used that booted the web servers on the lb-mgmt-lan? I want to make sure we update that and clarify for future users. Michael [1] https://review.openstack.org/399272 [2] https://review.openstack.org/399276 On Sat, Nov 19, 2016 at 9:46 PM, Yipei Niu <newy...@gmail.com> wrote: > Hi, Micheal, > > Thanks a lot for your comments. > > Please find the errors of o-cw.log in link > http://paste.openstack.org/show/589806/. Hope it will help. > > About the lb-mgmt-net, I just follow the guide of running LBaaS. If I create > a ordinary subnet with neutron for the two VMs, will it prevent the issue > you mentioned happening? > > Best regards, > Yipei > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev