yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #31703
[Bug 1439870] Re: Fixed IPs not being recorded in database
I think I have covered the reason for marking this invalid in my
previous comments.
** Changed in: nova
Status: Incomplete => Invalid
** Changed in: nova
Assignee: Sudipta Biswas (sbiswas7) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1439870
Title:
Fixed IPs not being recorded in database
Status in OpenStack Compute (Nova):
Invalid
Bug description:
When new VMs are spawned after deleting previous VMs, the new VMs
obtain completely new ips and the old ones are not recycled to reuse.
I looked into the mysql database to see where ips may be being stored
and accessed by openstack to determine what the next in line should
be, but didn' tmanage to find any ip information there. Has the
location of this storage changed out of the fixed_ips table?
Currently, this table is entirely empty:
MariaDB [nova]> select * from fixed_ips;
Empty set (0.00 sec)
despite having many vms running on two different networks:
mysql -e "select uuid, deleted, power_state, vm_state, display_name, host from nova.instances;"
+--------------------------------------+---------+-------------+----------+--------------+--------------+
| uuid | deleted | power_state | vm_state | display_name | host |
+--------------------------------------+---------+-------------+----------+--------------+--------------+
| 14600536-7ce1-47bf-8f01-1a184edb5c26 | 0 | 4 | error | Ctest | r001ds02.pcs |
| abb38321-5b74-4f36-b413-a057897b8579 | 0 | 4 | stopped | cent7 | r001ds02.pcs |
| 31cbb003-42d0-468a-be4d-81f710e29aef | 0 | 1 | active | centos7T2 | r001ds02.pcs |
| 4494fd8d-8517-4f14-95e6-fe5a6a64b331 | 0 | 1 | active | selin_test | r001ds02.pcs |
| 25505dc4-2ba9-480d-ba5a-32c2e91fc3c9 | 0 | 1 | active | 2NIC | r001ds02.pcs |
| baff8cef-c925-4dfb-ae90-f5f167f32e83 | 0 | 4 | stopped | kepairtest | r001ds02.pcs |
| 317e1fbf-664d-43a8-938a-063fd53b801d | 0 | 1 | active | test | r001ds02.pcs |
| 3a8c1a2d-1a4b-4771-8e62-ab1982759ecd | 0 | 1 | active | 3 | r001ds02.pcs |
| c4b2175a-296c-400c-bd54-16df3b4ca91b | 0 | 1 | active | 344 | r001ds02.pcs |
| ac02369e-b426-424d-8762-71ca93eacd0c | 0 | 4 | stopped | 333 | r001ds02.pcs |
| 504d9412-e2a3-492a-8bc1-480ce6249f33 | 0 | 1 | active | libvirt | r001ds02.pcs |
| cc9f6f06-2ba6-4ec2-94f7-3a795aa44cc4 | 0 | 1 | active | arger | r001ds02.pcs |
| 0a247dbf-58b4-4244-87da-510184a92491 | 0 | 1 | active | arger2 | r001ds02.pcs |
| 4cb85bbb-7248-4d46-a9c2-fee312f67f96 | 0 | 1 | active | gh | r001ds02.pcs |
| adf9de81-3986-4d73-a3f1-a29d289c2fe3 | 0 | 1 | active | az | r001ds02.pcs |
| 8396eabf-d243-4424-8ec8-045c776e7719 | 0 | 1 | active | sdf | r001ds02.pcs |
| 947905b5-7a2c-4afb-9156-74df8ed699c5 | 55 | 1 | deleted | yh | r001ds02.pcs |
| f690d7ed-f8d5-45a1-b679-e79ea4d3366f | 56 | 1 | deleted | tr | r001ds02.pcs |
| dd1aa5b1-c0ac-41f6-a6de-05be8963242f | 57 | 1 | deleted | ig | r001ds02.pcs |
| 42688a7d-2ba2-4d5a-973f-e87f87c32326 | 58 | 1 | deleted | td | r001ds02.pcs |
| 7c1014d8-237d-48f0-aa77-3aa09fff9101 | 59 | 1 | deleted | td2 | r001ds02.pcs |
+--------------------------------------+---------+-------------+----------+--------------+--------------+
I am using neutron networking with OVS. It is my understanding that
the mysql sqlalchemy is setup to leave old information accessible in
mysql, but deleting the associated information manually doesn't seem
to make a difference as to the fixed_ips issue I am experiencing. Are
there solutions for this?
nova --version : 2.20.0 ( 2014.2.1-1.el7 running on centOS7, epel-juno
release)
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1439870/+subscriptions
References