You can find the netruon client version by running: "neutron --version"
I have 4.1.2 installed.
I think you can update with "pip install --upgrade python-neutronclient"
This is a bit odd as I thought the error above was returned from neutron proper.
Michael
On Mon, Mar 28, 2016 at 10:06 AM, Kevin <email address hidden> wrote:
> Hi Micheal,
>
> I am getting the same issue still. I just stacked a new devstack on a
> new machine. It has the latest commit for neutron. I'm not too sure what
> version of neutronclient it's on. In the /usr/local/lib/python2.7/dist-
> packages/, I see a python_neutronclient-4.1.1.dist-info. How would I
> check for the neutronclient version? How would I update it?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1558934
>
> Title:
> Healthmonitor fails to spawn new amphora from spare pool
>
> Status in octavia:
> Fix Released
>
> Bug description:
> Active standby topology
> Spare amphora pool = 2
>
> When an amphora is stopped, the health monitor will correctly detect a
> stale amphora. However, the controller fails to configure a new
> amphora when it is allocating a new amphora from a spare amphora pool.
> It fails to plug the vip and raises an exception NotFound: Not Found.
>
> Gist of o-hm.log
> https://gist.github.com/anonymous/d6694757cc32d0d0626b#file-o-hm-log
>
> From agent log in amphora
> Amphora responds with 404 error to the plug_vip rest request
> 2016-03-17 23:21:47.199 568 WARNING werkzeug [-] * Debugger is active!
> 2016-03-17 23:21:47.224 568 INFO werkzeug [-] * Debugger pin code: 914-191-124
> 2016-03-17 23:22:32.480 568 INFO werkzeug [-] 192.168.0.3 - - [17/Mar/2016 23:22:32] "POST /0.5/plug/vip/10.0.0.3 HTTP/1.1" 404 -
>
> If i'm not using a spare amphora pool, the failover works correctly.
> No issues with creating and configuring new amphora.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/octavia/+bug/1558934/+subscriptions
Hi Kevin,
You can find the netruon client version by running: "neutron --version"
I have 4.1.2 installed.
I think you can update with "pip install --upgrade python- neutronclient"
This is a bit odd as I thought the error above was returned from neutron proper.
Michael
On Mon, Mar 28, 2016 at 10:06 AM, Kevin <email address hidden> wrote: lib/python2. 7/dist- neutronclient- 4.1.1.dist- info. How would I /bugs.launchpad .net/bugs/ 1558934 /gist.github. com/anonymous/ d6694757cc32d0d 0626b#file- o-hm-log vip/10. 0.0.3 HTTP/1.1" 404 - /bugs.launchpad .net/octavia/ +bug/1558934/ +subscriptions
> Hi Micheal,
>
> I am getting the same issue still. I just stacked a new devstack on a
> new machine. It has the latest commit for neutron. I'm not too sure what
> version of neutronclient it's on. In the /usr/local/
> packages/, I see a python_
> check for the neutronclient version? How would I update it?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Healthmonitor fails to spawn new amphora from spare pool
>
> Status in octavia:
> Fix Released
>
> Bug description:
> Active standby topology
> Spare amphora pool = 2
>
> When an amphora is stopped, the health monitor will correctly detect a
> stale amphora. However, the controller fails to configure a new
> amphora when it is allocating a new amphora from a spare amphora pool.
> It fails to plug the vip and raises an exception NotFound: Not Found.
>
> Gist of o-hm.log
> https:/
>
> From agent log in amphora
> Amphora responds with 404 error to the plug_vip rest request
> 2016-03-17 23:21:47.199 568 WARNING werkzeug [-] * Debugger is active!
> 2016-03-17 23:21:47.224 568 INFO werkzeug [-] * Debugger pin code: 914-191-124
> 2016-03-17 23:22:32.480 568 INFO werkzeug [-] 192.168.0.3 - - [17/Mar/2016 23:22:32] "POST /0.5/plug/
>
> If i'm not using a spare amphora pool, the failover works correctly.
> No issues with creating and configuring new amphora.
>
> To manage notifications about this bug go to:
> https:/