vm did not acquire an ipv4 address
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Invalid
|
Critical
|
ChenjieXu |
Bug Description
Brief Description
----------------
Instance schedules and shows as "ACTIVE" but getting into the instance there is no IP assigned
Severity
--------
Critical
Steps to Reproduce
------------------
1. Create an instance throw horizon or CLI with or without security group or keypar
openstack server create --image centos --flavor m1.medium --network public-net0 --
security-group security1 --key-name key1 <instance name>
2. Verify that your instance is up and active
openstack server list
+------
| ID | Name | Status | Networks | Image | Flavor |
+------
| d650a5de-
| e349334b-
+------
3. Verify that you instance has the same ip showed
sudo virsh console <instance>
Expected Behavior
------------------
The instance should have the same IP in order to perform simple communication through TCP or ICMP according with the default security group or custom made security group rules.
Actual Behavior
----------------
There is no assigned IP for any instance. Not communication even if you force the ip assigning the same showed before.
--Inside the Instance:
eth0: flags=4163<
inet6 fe80::f816:
ether fa:16:3e:88:9d:d9 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 32 bytes 8856 (8.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 6 bytes 416 (416.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 6 bytes 416 (416.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
The instance is showing the following error during booting up:
2s)[K[[
See 'systemctl status network.service' for details.
Starting Initial cloud-init job (metadata service crawler)...
[[32m OK [0m] Reached target Network.
Starting Dynamic System Tuning Daemon...
Starting Postfix Mail Transport Agent...
[ 304.828028] cloud-init[765]: Cloud-init v. 0.7.9 running 'init' at Tue, 05 Nov 2019 10:41:26 +0000. Up 304.80 seconds.
[ 304.859081] cloud-init[765]: ci-info: +++++++
[ 304.861210] cloud-init[765]: ci-info: +------
[ 304.863153] cloud-init[765]: ci-info: | Device | Up | Address | Mask | Scope | Hw-Address |
[ 304.865078] cloud-init[765]: ci-info: +------
[ 304.867040] cloud-init[765]: ci-info: | lo: | True | 127.0.0.1 | 255.0.0.0 | . | . |
[ 304.869118] cloud-init[765]: ci-info: | lo: | True | . | . | d | . |
[ 304.871125] cloud-init[765]: ci-info: | eth0: | True | . | . | . | fa:16:3e:88:9d:d9 |
[ 304.873062] cloud-init[765]: ci-info: | eth0: | True | . | . | d | fa:16:3e:88:9d:d9 |
[ 304.875019] cloud-init[765]: ci-info: +------
[[32m OK [0m] Started Dynamic System Tuning Daemon.
[ 305.000066] cloud-init[765]: 2019-11-05 10:41:26,461 - url_helper.
No matter the image, centos or cirros, the problem is the same
Reproducibility
---------------
100 % with all configurations
System Configuration
-------
All configurations with IPV4
Branch/Pull Time/Commit
-------
###
### StarlingX
### Built from master
###
OS="centos"
SW_VERSION="19.09"
BUILD_TARGET="Host Installer"
BUILD_TYPE="Formal"
BUILD_ID=
JOB="STX_
<email address hidden>"
BUILD_NUMBER="303"
BUILD_HOST=
BUILD_DATE=
Last Pass
---------
BUILD_ID=
Timestamp/Logs
--------------
Attached
Test Activity
-------------
Regression 3.0
Assigning to networking PL for next steps