<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>Hi Yipei,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have meant to add this as a config option, but in the interim you can do the following to disable the automatic cleanup by disabling the revert flow in taskflow:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>octavia/common/base_taskflow.py line 37 add “<span style='font-size:9.0pt;font-family:Consolas;color:#183691'>never_resolve=True,” to the engine load parameters.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:Consolas;color:#183691'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:Consolas;color:#183691'>Michael</span><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>From:</b> Yipei Niu [mailto:newypei@gmail.com] <br><b>Sent:</b> Monday, June 26, 2017 11:34 PM<br><b>To:</b> OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org><br><b>Subject:</b> Re: [openstack-dev] [octavia] fail to plug vip to amphora<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Hi, Micheal,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thanks a lot for your help, but I still have one question. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>In Octavia, once the controller worker fails plugging VIP to the amphora, the amphora is deleted immediately, making it impossible to trace the error. How to prevent Octavia from stopping and deleting the amphora? <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Best regards,<o:p></o:p></p></div><div><p class=MsoNormal>Yipei <o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Mon, Jun 26, 2017 at 11:21 AM, Yipei Niu <<a href="mailto:newypei@gmail.com" target="_blank">newypei@gmail.com</a>> wrote:<o:p></o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><p class=MsoNormal>Hi, all,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I am trying to create a load balancer in octavia. The amphora can be booted successfully, and can be reached via icmp. However, octavia fails to plug vip to the amphora through the amphora client api and returns 500 status code, causing some errors as follows.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal> |__Flow 'octavia-create-loadbalancer-flow': InternalServerError: Internal Server Error<o:p></o:p></p></div><div><p class=MsoNormal>2017-06-21 09:49:35.864 25411 ERROR octavia.controller.worker.controller_worker Traceback (most recent call last):<o:p></o:p></p></div><div><p class=MsoNormal>2017-06-21 09:49:35.864 25411 ERROR octavia.controller.worker.controller_worker File "/usr/local/lib/python2.7/dist-packages/taskflow/engines/action_engine/executor.py", line 53, in _execute_task<o:p></o:p></p></div><div><p class=MsoNormal>2017-06-21 09:49:35.864 25411 ERROR octavia.controller.worker.controller_worker result = task.execute(**arguments)<o:p></o:p></p></div><div><p class=MsoNormal>2017-06-21 09:49:35.864 25411 ERROR octavia.controller.worker.controller_worker File "/opt/stack/octavia/octavia/controller/worker/tasks/amphora_driver_tasks.py", line 240, in execute<o:p></o:p></p></div><div><p class=MsoNormal>2017-06-21 09:49:35.864 25411 ERROR octavia.controller.worker.controller_worker amphorae_network_config)<o:p></o:p></p></div><div><p class=MsoNormal>2017-06-21 09:49:35.864 25411 ERROR octavia.controller.worker.controller_worker File "/opt/stack/octavia/octavia/controller/worker/tasks/amphora_driver_tasks.py", line 219, in execute<o:p></o:p></p></div><div><p class=MsoNormal>2017-06-21 09:49:35.864 25411 ERROR octavia.controller.worker.controller_worker amphora, loadbalancer, amphorae_network_config)<o:p></o:p></p></div><div><p class=MsoNormal>2017-06-21 09:49:35.864 25411 ERROR octavia.controller.worker.controller_worker File "/opt/stack/octavia/octavia/amphorae/drivers/haproxy/rest_api_driver.py", line 137, in post_vip_plug<o:p></o:p></p></div><div><p class=MsoNormal>2017-06-21 09:49:35.864 25411 ERROR octavia.controller.worker.controller_worker net_info)<o:p></o:p></p></div><div><p class=MsoNormal>2017-06-21 09:49:35.864 25411 ERROR octavia.controller.worker.controller_worker File "/opt/stack/octavia/octavia/amphorae/drivers/haproxy/rest_api_driver.py", line 378, in plug_vip<o:p></o:p></p></div><div><p class=MsoNormal>2017-06-21 09:49:35.864 25411 ERROR octavia.controller.worker.controller_worker return exc.check_exception(r)<o:p></o:p></p></div><div><p class=MsoNormal>2017-06-21 09:49:35.864 25411 ERROR octavia.controller.worker.controller_worker File "/opt/stack/octavia/octavia/amphorae/drivers/haproxy/exceptions.py", line 32, in check_exception<o:p></o:p></p></div><div><p class=MsoNormal>2017-06-21 09:49:35.864 25411 ERROR octavia.controller.worker.controller_worker raise responses[status_code]()<o:p></o:p></p></div><div><p class=MsoNormal>2017-06-21 09:49:35.864 25411 ERROR octavia.controller.worker.controller_worker InternalServerError: Internal Server Error<o:p></o:p></p></div><div><p class=MsoNormal>2017-06-21 09:49:35.864 25411 ERROR octavia.controller.worker.controller_worker<o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>To fix the problem, I log in the amphora and find that there is one http server process is listening on port 9443, so I think the amphora api services is active. But do not know how to further investigate what error happens inside the amphora api service and solve it? Look forward to your valuable comments.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Best regards,<o:p></o:p></p></div><div><p class=MsoNormal>Yipei <o:p></o:p></p></div></div></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>