Ask Your Question
0

CentOS image active but not reachable [SOLVED] [closed]

asked 2017-04-16 12:22:39 -0500

yucefrizk gravatar image

updated 2017-04-19 01:40:33 -0500

Hello,

I'm trying OpenStack on two virtual machines (Controller and Compute), and I'm following OpenStack documentation for this. New server with CirrOS image is working fine, the image is reachable by ping and SSH, but I'm not able to do the same using a CentOS image. the CentOS server is status is ACTIVE but its IP address is not accessible

[root@controller ~]# openstack server list +--------------------------------------+--------------+--------+---------------------+------------+ | ID | Name | Status | Networks | Image Name | +--------------------------------------+--------------+--------+---------------------+------------+ | eff00a87-acb0-4c57-825c-2f2532b8987d | myinstance | ACTIVE | provider=10.0.0.103 | myImage | +--------------------------------------+--------------+--------+---------------------+------------+ [root@controller ~]#

[root@controller ~]# ping 10.0.0.103 PING 10.0.0.103 (10.0.0.103) 56(84) bytes of data. From 10.0.0.11 icmp_seq=1 Destination Host Unreachable From 10.0.0.11 icmp_seq=2 Destination Host Unreachable From 10.0.0.11 icmp_seq=3 Destination Host Unreachable

Since I have no issues with the CirrOS image, I'm expecting problems with the CentOS image and not the configuration of OpenStack components.

I'm following the instructions on https://docs.openstack.org/image-guid... to create the image and the firewall is turned off on the image. (I'm creating the image on VirtualBox and converting OVA to img using qemu-img)

Any suggestions please?

Thank you.

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by yucefrizk
close date 2017-04-19 02:18:20.204199

Comments

Are the Cirros and Centos instances on the same network? If yes, find out whether Centos has received its IP address. openstack console log show should do that, or perhaps you can log on via the VNC console. The VNC console also allows you to check connectivity from within the instance.

Bernd Bausch gravatar imageBernd Bausch ( 2017-04-17 00:35:53 -0500 )edit

2 answers

Sort by ยป oldest newest most voted
0

answered 2017-04-17 03:20:53 -0500

Laurent_bcn gravatar image

I suggest to make a test with a known working image with cloud-init pre-installed : http://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud.qcow2

You can also chek your security group.

edit flag offensive delete link more
0

answered 2017-04-19 00:52:06 -0500

yucefrizk gravatar image

updated 2017-04-19 02:16:18 -0500

Hello,

Thank you for your answers, in fact I already tried with an image from http://cloud.centos.org and had the same problem.

After getting access to the console, i found a kernel panic message: "kernel panic not syncing io apic + timer doesn't work" so I rebuilt a new image with noapic in the grub configuration. After this step, the instance was booting correctly however I had issues with the network configuration.

The default network interface name in Centos 7 is enp0s3, however when I logged in to the console, it seems that the network service is trying to bring eth0 up. So I changed enp0s3 to eth0 (/sbin/ip link set enp0s3 down && /sbin/ip link set enp0s3 name eth0)

Following these two steps (noapic in the grub configuration and changing the network interface name) the instance is booting correctly and accessible.

Thank you

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2017-04-16 12:22:39 -0500

Seen: 584 times

Last updated: Apr 19 '17