nova absolute-limits floating ip count is incorrect in a neutron based deployment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Low
|
Unassigned | ||
neutron |
Invalid
|
Undecided
|
Unassigned | ||
nova (Ubuntu) |
In Progress
|
Low
|
Satyanarayana Patibandla |
Bug Description
1.
$ lsb_release -rd
Description: Ubuntu 14.04 LTS
Release: 14.04
2.
$ apt-cache policy python-novaclient
python-novaclient:
Installed: 1:2.17.0-0ubuntu1
Candidate: 1:2.17.0-0ubuntu1
Version table:
*** 1:2.17.0-0ubuntu1 0
500 http://
100 /var/lib/
3. nova absolute-limits should report the correct value of allocated floating ips
4. nova absolute-limits shows 0 floating ips when I have 5 allocated
$ nova absolute-limits | grep Floating
| totalFloatingIp
| maxTotalFloatingIps | 10 |
$ nova floating-ip-list
+------
| Ip | Server Id | Fixed Ip | Pool |
+------
| 10.98.191.146 | | - | ext_net |
| 10.98.191.100 | | 10.5.0.242 | ext_net |
| 10.98.191.138 | | 10.5.0.2 | ext_net |
| 10.98.191.147 | | - | ext_net |
| 10.98.191.102 | | - | ext_net |
+------
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: python-novaclient 1:2.17.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
Date: Wed Oct 1 15:19:08 2014
Ec2AMI: ami-00000001
Ec2AMIManifest: FIXME
Ec2Availability
Ec2InstanceType: m1.small
Ec2Kernel: aki-00000002
Ec2Ramdisk: ari-00000002
PackageArchitec
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: python-novaclient
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in python-novaclient (Ubuntu): | |
importance: | Undecided → Medium |
Changed in nova (Ubuntu): | |
assignee: | nobody → Satyanarayana Patibandla (satya-patibandla) |
Changed in nova: | |
status: | Confirmed → Triaged |
Changed in nova (Ubuntu): | |
status: | Triaged → In Progress |
information type: | Public Security → Public |
Changed in nova: | |
assignee: | nobody → Anusha Unnam (anusha-unnam) |
Changed in nova: | |
assignee: | Anusha Unnam (anusha-unnam) → nobody |
Changed in neutron: | |
status: | Incomplete → Invalid |
It looks like nova is only accounting for floating ip's its directly managing (nova-network) rather than those being managed by neutron as in this deployment.
Marking 'Confirmed' - I see the same thing on an icehouse deployment; I suspect this is in nova, not the client.