Ask Your Question
1

instance only show the IP on dashboard but not inside the VM

asked 2017-04-26 03:03:12 -0600

MuhammadAwais gravatar image

updated 2017-04-27 03:46:00 -0600

VM is not getting the IP but only IP is showing on dashboard, I am using NEWtow relaese.

Please advise, below are the out put

[root@controller /]# openstack compute service list
+----+------------------+------------+----------+---------+-------+----------------------------+
| ID | Binary           | Host       | Zone     | Status  | State | Updated At                 |
+----+------------------+------------+----------+---------+-------+----------------------------+
|  1 | nova-conductor   | controller | internal | enabled | up    | 2017-04-26T07:59:10.000000 |
|  2 | nova-scheduler   | controller | internal | enabled | up    | 2017-04-26T07:59:10.000000 |
|  3 | nova-consoleauth | controller | internal | enabled | up    | 2017-04-26T07:59:13.000000 |
|  7 | nova-compute     | compute    | nova     | enabled | up    | 2017-04-26T07:59:12.000000 |
+----+------------------+------------+----------+---------+-------+----------------------------+
[root@controller /]# openstack network agent list
+--------------------------------------+--------------------+------------+-------------------+-------+-------+---------------------------+
| ID                                   | Agent Type         | Host       | Availability Zone | Alive | State | Binary                    |
+--------------------------------------+--------------------+------------+-------------------+-------+-------+---------------------------+
| 2f8aaefe-6976-46d8-9a0b-977f0e119646 | Linux bridge agent | controller | None              | True  | UP    | neutron-linuxbridge-agent |
| 710f87e0-3183-4377-b85a-6ddf52cb5f44 | Linux bridge agent | compute    | None              | True  | UP    | neutron-linuxbridge-agent |
| 87c13aef-8ded-4417-9650-1a65fe6ee507 | L3 agent           | controller | nova              | True  | UP    | neutron-l3-agent          |
| a4d899b7-c4ba-4f2c-847b-deeee31431ea | DHCP agent         | controller | nova              | True  | UP    | neutron-dhcp-agent        |
| fb980855-9790-476c-9dff-d1ea197b3896 | Metadata agent     | controller | None              | True  | UP    | neutron-metadata-agent    |
+--------------------------------------+--------------------+------------+-------------------+-------+-------+---------------------------+
[root@controller /]#


[root@controller /]# openstack network show provider
+---------------------------+--------------------------------------+
| Field                     | Value                                |
+---------------------------+--------------------------------------+
| admin_state_up            | UP                                   |
| availability_zone_hints   |                                      |
| availability_zones        | nova                                 |
| created_at                | 2017-04-26T18:42:57Z                 |
| description               |                                      |
| id                        | eabf1c8b-2744-499a-b6ad-1921e1fe8351 |
| ipv4_address_scope        | None                                 |
| ipv6_address_scope        | None                                 |
| is_default                | False                                |
| mtu                       | 1500                                 |
| name                      | provider                             |
| port_security_enabled     | True                                 |
| project_id                | 7df83207c82846d1a0b18d0baa36b616     |
| project_id                | 7df83207c82846d1a0b18d0baa36b616     |
| provider:network_type     | flat                                 |
| provider:physical_network | provider                             |
| provider:segmentation_id  | None                                 |
| revision_number           | 6                                    |
| router:external           | External                             |
| shared                    | True                                 |
| status                    | ACTIVE                               |
| subnets                   | f31bfba2-62f0-4844-bc8f-6af9daec614c |
| tags                      | []                                   |
| updated_at                | 2017-04-26T18:43:25Z                 |
+---------------------------+--------------------------------------+


[linux_bridge]
physical_interface_mappings = provider:enp6s0

[vxlan]
enable_vxlan = True
local_ip = 192.168.1.4
l2_population = True

[securitygroup]
enable_security_group = True
firewall_driver = neutron.agent.linux.iptables_firewall.IptablesFirewallDriver
edit retag flag offensive close merge delete

Comments

My guess is that the instance doesn't receive the DHCP reply. There are other possibilities, e.g. the instance doesn't use DHCP or you didn't configure DHCP on the network to which the instance is connected.

Do you see anything about DCHP or IP addresses in the console log? Are other instances OK?

Bernd Bausch gravatar imageBernd Bausch ( 2017-04-26 04:51:04 -0600 )edit

thanks for your response, its my first VM and DHCP is working but cannot get the IP, I have run the ifup eth0 but its showing

dashboard is showing the IP but VM is not get the IP from DHCP

no lease, failing

MuhammadAwais gravatar imageMuhammadAwais ( 2017-04-26 05:57:03 -0600 )edit

I have check one more thing, on the compute node my provider interface is showing off. I have changed the interface setting dhcp to none but its automatically revert back to dhcp. I have seen on GUI

MuhammadAwais gravatar imageMuhammadAwais ( 2017-04-26 06:08:47 -0600 )edit

Starting network... udhcpc (v1.20.1) started Sending discover... Sending discover... no lease, failing

MuhammadAwais gravatar imageMuhammadAwais ( 2017-04-26 06:16:16 -0600 )edit

So, your VM requests an IP aadress through DHCP, but doesn't get one. Perhaps you have NetworkManager running, and it interferes with your NW config. Your servers' interfaces should have static IPs or no IP.

Bernd Bausch gravatar imageBernd Bausch ( 2017-04-26 09:41:20 -0600 )edit

5 answers

Sort by ยป oldest newest most voted
0

answered 2018-03-06 06:53:42 -0600

AB239 gravatar image

I am also facing this issue in Newton release. Anyone got solution to this problem? When I manually add IP in interface file, I can see it in 'ip addr show'. Otherwise, dhclient -6 and ifup fail.

edit flag offensive delete link more
0

answered 2017-04-27 03:48:46 -0600

anurag-jindal29 gravatar image

Check the disk size of the flavor that you are using to spawn the instance. You may need to add few extra GB of disk.

edit flag offensive delete link more
0

answered 2017-05-20 06:37:41 -0600

lost007 gravatar image

I am facing the same problem, did you find a solution ?

edit flag offensive delete link more
0

answered 2017-04-28 03:23:52 -0600

eblock gravatar image

DHCP requests into external networks don't work per default. I don't know how to change that, but you can use cloud-init (and config-drive) to provide an ip address to an instance in an external network. That's how we configure our VMs with interfaces in external networks. So basically, it's something like

nova boot --flavor <FLAVOR> --image <IMAGE> --nic port-id=<PORT-ID> --config-drive true <YOUR-VM>

The referenced port should be created prior to the instance, of course. Alternatively, you can specify an ip address instead of a specific port:

... --nic net-id=<NET-ID>,v4-fixed-ip=<YOUR-IP>

Cloud-init has to be active inside the used image, and if everything works, it will configure the VM's nic according to your configuration. Hope this helps!

edit flag offensive delete link more
0

answered 2017-04-27 01:24:33 -0600

amitabh sinha gravatar image

@MuhammadAwais when you create Vm in admin network or external network in that that case you will be able to see the ip on dashboard but you will not be able to see the ip inside the vm...When you create the Vm in tenant_network then only you will be in a position to get IP inside the IP.

edit flag offensive delete link more

Comments

in both cases I am unable to get the IPs, please advise

MuhammadAwais gravatar imageMuhammadAwais ( 2017-04-27 02:34:41 -0600 )edit

My environment is Mitaka. I am also facing the same issue couldn't assign an ip address to vm but on dashboard I can see the ip address is assigned to vm. I have deploy few times through packstck and every time same issue. if you resolved the issue please provide me solution. Thanks Khan

mkhan gravatar imagemkhan ( 2017-05-08 15:28:11 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

2 followers

Stats

Asked: 2017-04-26 03:03:12 -0600

Seen: 2,103 times

Last updated: Mar 06 '18