Ask Your Question
0

Nova instance not accessible after OS update and reboot

asked 2014-01-11 02:47:24 -0500

Clarence gravatar image

I am running Openstack Havana release on CentOS 6.5. And have 2 servers (1 controller, and 1 compute node). On the compute node, I created an instance (also running CentOS 6.5). The instance was running fine for some time.

However, one day after I perform OS update (running the yum update command) on both the instance, compute node and controller, and reboot, I found that I am not able to access the instance anymore. From command line and dashboard, everything seems normal, I can see my instance, start it, and the status shows "running".

What I did was follows: - OS update on the instance (yum update), and then shutdown the instance in dashboard - OS update on the compute node (yum update), and then reboot the compute node - OS update on the controller node (yum update), and then reboot the controller node

After I did the above, I check both nodes and find all openstack services are running normally. Then I login to dashboard and start my instance, and the instance started normally as shown in the dashboard.

However, I found that I am not able to ping the machine, so no way to login to the machine. I go to the instance folder and the console-log file is empty. I use nova reboot and still not able to access the machine.

I tried to launch a new instance and everything works. I can ping the new instance and login to it. I tried to browse through all the log files as mentioned in the operation guide but still don't know how to identify the problem.

I am quite new to Openstack, can someone advice me on how to troubleshoot my instance. What I want to do first is to able to see whether the instance was really booted successfully or not.

Thanks a lot in advance Clarence

edit retag flag offensive close merge delete

Comments

On the compute node, can you confirm that the instance is actually running if you do a "virsh list"?

jtopjian gravatar imagejtopjian ( 2014-01-11 07:13:21 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2014-01-14 18:52:27 -0500

Clarence gravatar image

Thanks a lot for your response.

I did checked and the following is the outcome of the virsh list command:

Id Name State

7 instance-00000027 running 8 instance-00000028 running

The instance having problem is 27. I also tried to suspend and resume the instance and still no luck.

Any further advice will be much welcome.

Clarence

edit flag offensive delete link more

Comments

Can you try doing "nova reboot --hard <instance id="">"?

jtopjian gravatar imagejtopjian ( 2014-01-15 03:29:32 -0500 )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

1 follower

Stats

Asked: 2014-01-11 02:47:24 -0500

Seen: 303 times

Last updated: Jan 14 '14