Network info not always displayed for a created instance

Bug #1740241 reported by Gleb Zimin
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Expired
Undecided
Unassigned

Bug Description

I'am trying to deploy DVR Multi-node + Provider network openstack configuration. So I have 3 nodes - Controller(All-in-one), Compute node and Network node. I created private network, where I launch my instances. The problem is when I am trying to launch instance on my compute node it's creating without Network IP. I'am using Openstack CLI to launch instance. So, command look like this:

$ openstack server create --image cirros-0.3.4-x86_64-uec --flavor 1 --nic net-id=13e6c93a-0b87-4b18-9f44-7c9d78682a80 --availability-zone nova:gzimin-dev2 deb11_dev2

As a result i get:

$ openstack server show deb11_dev2
+-------------------------------------+----------------------------------------------------------------+
| Field | Value |
+-------------------------------------+----------------------------------------------------------------+
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-AZ:availability_zone | nova |
| OS-EXT-SRV-ATTR:host | gzimin-dev2 |
| OS-EXT-SRV-ATTR:hypervisor_hostname | gzimin-dev2 |
| OS-EXT-SRV-ATTR:instance_name | instance-00000034 |
| OS-EXT-STS:power_state | Running |
| OS-EXT-STS:task_state | None |
| OS-EXT-STS:vm_state | active |
| OS-SRV-USG:launched_at | 2017-12-26T10:01:59.000000 |
| OS-SRV-USG:terminated_at | None |
| accessIPv4 | |
| accessIPv6 | |
| addresses | |
| config_drive | |
| created | 2017-12-26T10:01:50Z |
| flavor | m1.tiny (1) |
| hostId | 4f720feca9816d41461a56a37d5e07faf7c32b8c095a80146fdc441e |
| id | d757178e-0357-48e7-a827-9991378543bd |
| image | cirros-0.3.4-x86_64-uec (37f39bd9-8bb7-4bb8-b6f2-c3c5d98d7955) |
| key_name | None |
| name | deb11_dev2 |
| progress | 0 |
| project_id | ea95a2a8d75f48dbb5a90b7787877fbd |
| properties | |
| security_groups | name='default' |
| status | ACTIVE |
| updated | 2017-12-26T10:02:00Z |
| user_id | 8d34357343504c01ba0af196c8f9c56c |
| volumes_attached | |
+-------------------------------------+----------------------------------------------------------

As we can see field "addresses" is empty. And then when I'am trying to allocate floating IP to this instance i get error like this:

$ openstack server add floating ip deb11_dev2 172.18.171.174
Instance network is not ready yet (HTTP 400) (Request-ID: req-b5278c5d-220a-436b-8bf6-dd22e204b316)

But some times when I create instance as previous it's get IP and all work's fine. I can't understand on what does this bug depend. And also all this nodes with and without IP has IP in Horizon.
I attached all my local.conf files of all nodes and nova-api logs.

Revision history for this message
Gleb Zimin (gzimin) wrote :
Revision history for this message
Gleb Zimin (gzimin) wrote :

This is n-api logs of creating instance

Revision history for this message
Gleb Zimin (gzimin) wrote :

So i didn't say that this is Openstack Ocata version 15.0.8.

Revision history for this message
Gleb Zimin (gzimin) wrote :

On the Neutron side all works fine. Ports are binding and IP's are available.
I tried to launch a lot of instance at the same time and some of them get ip's and some don't get.

Gleb Zimin (gzimin)
summary: - Creating instance without IP
+ Network info not always displayed for a created instance
Revision history for this message
Gleb Zimin (gzimin) wrote :

What I found at this moment:
When I am want to display instance, network info (nw_info) of this instance is empty. And also in DB in allocated instances there is no record about this instance.

tags: added: network openstack-version.ocata
Revision history for this message
Sylvain Bauza (sylvain-bauza) wrote :

We build the networks by the compute manager, see https://github.com/openstack/nova/blob/9319a0a/nova/compute/manager.py#L2159

Could you please use the DEBUG level for your computes, and give us the nova-compute log for that instance ? Looks like you have a configuration problem for your services trying to ask Neutron.

Changed in nova:
status: New → Incomplete
Revision history for this message
Gleb Zimin (gzimin) wrote :

Sorry Sylvain, but now i can not reproduce this bug again.

Revision history for this message
Jacolex (jacolex) wrote :
Download full text (8.5 KiB)

Hi
I have the same issue. The only way to fix I found is run openstack port delete and then attach new port and update fixed ip for it (detaching interface is not working, because conmpute node throws error that port is not attached).

Example of broken network on instance.
# openstack server show 248d1672-88e2-43c2-93f3-379884109f23
+-------------------------------------+----------------------------------------------------------+
| Field | Value |
+-------------------------------------+----------------------------------------------------------+
| OS-DCF:diskConfig | AUTO |
| OS-EXT-AZ:availability_zone | ----- |
| OS-EXT-SRV-ATTR:host | lab-cn-h115 |
| OS-EXT-SRV-ATTR:hypervisor_hostname | lab-cn-h115 |
| OS-EXT-SRV-ATTR:instance_name | instance-0000f3c7 |
| OS-EXT-STS:power_state | Running |
| OS-EXT-STS:task_state | None |
| OS-EXT-STS:vm_state | active |
| OS-SRV-USG:launched_at | 2017-08-30T13:55:34.000000 |
| OS-SRV-USG:terminated_at | None |
| accessIPv4 | |
| accessIPv6 | |
| addresses | |
| config_drive | |
| created | 2017-08-30T13:54:47Z |
| flavor | s.16VCPU_32GB (s16-32) |
| hostId | 5915f20ff98db4c228b7415339917b2b9d5673e43f25a5a7b205523b |
| id | 248d1672-88e2-43c2-93f3-379884109f23 |
| image | |
| key_name | ... |
| name | instancename |
| progress | 0 |
| project_id | 8cb1b772ccbf4d3d82d6a72f31053564 |
| properties | |
| security_groups | name='ssh' |
| | name='default' ...

Read more...

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]

Changed in nova:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.