yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #11339
[Bug 1290568] [NEW] Conductor support for networking on Icehouse
Public bug reported:
I'm updating the installation guide for Icehouse. Based on the following
blueprint, I removed the database configuration keys from nova.conf on
the compute node in my test environment.
https://blueprints.launchpad.net/nova/+spec/nova-network-objects
However, when attempting to boot an instance, the Nova network service
fails to retrieve network information from the controller. Adding the
the database keys resolves the problem. I'm using the
2014.1~b3-0ubuntu1~cloud0 packages on Ubuntu 12.04.
Here's my network configuration and instance boot information:
matt@hst-osctl5:~$ nova net-list
+--------------------------------------+-------+------------------+
| ID | Label | CIDR |
+--------------------------------------+-------+------------------+
| a4fd0905-2589-4cda-b1d2-d2ec5e4ec50d | demo | 172.24.246.24/29 |
+--------------------------------------+-------+------------------+
matt@hst-osctl5:~$ nova boot --flavor 1 --image cirros-0.3.1-x86_64 --key-name demo test1
+--------------------------------------+------------------------------------------------------------+
| Property | Value |
+--------------------------------------+------------------------------------------------------------+
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-AZ:availability_zone | nova |
| OS-EXT-STS:power_state | 0 |
| OS-EXT-STS:task_state | scheduling |
| OS-EXT-STS:vm_state | building |
| OS-SRV-USG:launched_at | - |
| OS-SRV-USG:terminated_at | - |
| accessIPv4 | |
| accessIPv6 | |
| adminPass | bDNSwTHU77ru |
| config_drive | |
| created | 2014-03-10T21:33:24Z |
| flavor | m1.tiny (1) |
| hostId | |
| id | 85a3a620-6419-4f6f-a540-5e85c4213189 |
| image | cirros-0.3.1-x86_64 (a768f831-0515-4a42-b4ef-b9492512c6f1) |
| key_name | demo |
| metadata | {} |
| name | test1 |
| os-extended-volumes:volumes_attached | [] |
| progress | 0 |
| security_groups | default |
| status | BUILD |
| tenant_id | f2908e1135c1435f856650b674e665fb |
| updated | 2014-03-10T21:33:24Z |
| user_id | 65b3a89d2990456887544410ad875d92 |
+--------------------------------------+------------------------------------------------------------+
Due to size, I'm attaching the output from nova-network.log when
attempting to boot an instance.
** Affects: nova
Importance: Undecided
Status: New
** Attachment added: "nova-network.log"
https://bugs.launchpad.net/bugs/1290568/+attachment/4017268/+files/nova-network.log
--
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/1290568
Title:
Conductor support for networking on Icehouse
Status in OpenStack Compute (Nova):
New
Bug description:
I'm updating the installation guide for Icehouse. Based on the
following blueprint, I removed the database configuration keys from
nova.conf on the compute node in my test environment.
https://blueprints.launchpad.net/nova/+spec/nova-network-objects
However, when attempting to boot an instance, the Nova network service
fails to retrieve network information from the controller. Adding the
the database keys resolves the problem. I'm using the
2014.1~b3-0ubuntu1~cloud0 packages on Ubuntu 12.04.
Here's my network configuration and instance boot information:
matt@hst-osctl5:~$ nova net-list
+--------------------------------------+-------+------------------+
| ID | Label | CIDR |
+--------------------------------------+-------+------------------+
| a4fd0905-2589-4cda-b1d2-d2ec5e4ec50d | demo | 172.24.246.24/29 |
+--------------------------------------+-------+------------------+
matt@hst-osctl5:~$ nova boot --flavor 1 --image cirros-0.3.1-x86_64 --key-name demo test1
+--------------------------------------+------------------------------------------------------------+
| Property | Value |
+--------------------------------------+------------------------------------------------------------+
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-AZ:availability_zone | nova |
| OS-EXT-STS:power_state | 0 |
| OS-EXT-STS:task_state | scheduling |
| OS-EXT-STS:vm_state | building |
| OS-SRV-USG:launched_at | - |
| OS-SRV-USG:terminated_at | - |
| accessIPv4 | |
| accessIPv6 | |
| adminPass | bDNSwTHU77ru |
| config_drive | |
| created | 2014-03-10T21:33:24Z |
| flavor | m1.tiny (1) |
| hostId | |
| id | 85a3a620-6419-4f6f-a540-5e85c4213189 |
| image | cirros-0.3.1-x86_64 (a768f831-0515-4a42-b4ef-b9492512c6f1) |
| key_name | demo |
| metadata | {} |
| name | test1 |
| os-extended-volumes:volumes_attached | [] |
| progress | 0 |
| security_groups | default |
| status | BUILD |
| tenant_id | f2908e1135c1435f856650b674e665fb |
| updated | 2014-03-10T21:33:24Z |
| user_id | 65b3a89d2990456887544410ad875d92 |
+--------------------------------------+------------------------------------------------------------+
Due to size, I'm attaching the output from nova-network.log when
attempting to boot an instance.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1290568/+subscriptions
Follow ups
References
