Shulou(Shulou.com)05/31 Report--

This article will explain in detail the example analysis of resize error debugging in the ice version. The content of the article is of high quality, so the editor will share it with you for reference. I hope you will have some understanding of the relevant knowledge after reading this article.

117 is shared by the control node and the compute node:

Nova-debug resize fefe2ba2-69dc-46dc-b337-da2788d94d49 4

The compute log on 117 reported an error:

Vim / var/log/nova/compute.log

[instance: b4d33c9d-c8b1-49e4-9f50-91f845d4115f] Setting instance vm_state to ERROR

2015-04-22 16 49e4 28V 22.435 3802 TRACE nova.compute.manager [instance: b4d33c9d-c8b1-49e4-9f50-91f845d4115f] Traceback (most recent call last):

2015-04-22 16 49e4 28V 22.435 3802 TRACE nova.compute.manager [instance: b4d33c9d-c8b1-49e4-9f50-91f845d4115f] File "/ usr/lib/python2.6/site-packages/nova/compute/manager.py", line 5531, in _ error_out_instance_on_exception

2015-04-22 16 49e4 28V 22.435 3802 TRACE nova.compute.manager [instance: b4d33c9d-c8b1-49e4-9f50-91f845d4115f] yield

2015-04-22 16 49e4 28V 22.435 3802 TRACE nova.compute.manager [instance: b4d33c9d-c8b1-49e4-9f50-91f845d4115f] File "/ usr/lib/python2.6/site-packages/nova/compute/manager.py", line 3428, in resize_instance

2015-04-22 16 49e4 28V 22.435 3802 TRACE nova.compute.manager [instance: b4d33c9d-c8b1-49e4-9f50-91f845d4115f] block_device_info)

2015-04-22 16 49e4 28V 22.435 3802 TRACE nova.compute.manager [instance: b4d33c9d-c8b1-49e4-9f50-91f845d4115f] File "/ usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py", line 5059, in migrate_disk_and_power_off

2015-04-22 16 TRACE nova.compute.manager 28V 22.435 3802 TRACE nova.compute.manager [instance: b4d33c9d-c8b1-49e4-9f50-91f845d4115f] utils.execute ('ssh', dest,' mkdir','- packs, inst_base)

2015-04-22 16 TRACE nova.compute.manager 2815 22.435 3802 TRACE nova.compute.manager [instance: b4d33c9d-c8b1-49e4-9f50-91f845d4115f] File "/ usr/lib/python2.6/site-packages/nova/utils.py", line 164, in execute

2015-04-22 16 49e4 28V 22.435 3802 TRACE nova.compute.manager [instance: b4d33c9d-c8b1-49e4-9f50-91f845d4115f] return processutils.execute (* cmd, * * kwargs)

2015-04-22 16 49e4 28V 22.435 3802 TRACE nova.compute.manager [instance: b4d33c9d-c8b1-49e4-9f50-91f845d4115f] File "/ usr/lib/python2.6/site-packages/nova/openstack/common/processutils.py", line 193, in execute

2015-04-22 16 49e4 28V 22.435 3802 TRACE nova.compute.manager [instance: b4d33c9d-c8b1-49e4-9f50-91f845d4115f] cmd=' '.join (cmd))

2015-04-22 16 49e4 28V 22.435 3802 TRACE nova.compute.manager [instance: b4d33c9d-c8b1-49e4-9f50-91f845d4115f] ProcessExecutionError: Unexpected error while running command.

2015-04-22 16 49e4 28V 22.435 3802 TRACE nova.compute.manager [instance: b4d33c9d-c8b1-49e4-9f50-91f845d4115f] Command: ssh 192.168.10.114 mkdir-p / var/lib/nova/instances/b4d33c9d-c8b1-49e4-9f50-91f845d4115f

2015-04-22 16 TRACE nova.compute.manager 2815 22.435 3802 TRACE nova.compute.manager [instance: b4d33c9d-c8b1-49e4-9f50-91f845d4115f] Exit code: 255

2015-04-22 16 49e4 28V 22.435 3802 TRACE nova.compute.manager [instance: b4d33c9d-c8b1-49e4-9f50-91f845d4115f] Stdout:''

2015-04-22 16 49e4 28V 22.435 3802 TRACE nova.compute.manager [instance: b4d33c9d-c8b1-49e4-9f50-91f845d4115f] Stderr: 'Host key verification failed.\ r\ n'

2015-04-22 16 49e4 28V 22.435 3802 TRACE nova.compute.manager [instance: b4d33c9d-c8b1-49e4-9f50-91f845d4115f]

2015-04-22 16 ERROR oslo.messaging.rpc.dispatcher 2818 22.818 3802 Exception during message handling: Unexpected error while running command.

Command: ssh 192.168.10.114 mkdir-p / var/lib/nova/instances/b4d33c9d-c8b1-49e4-9f50-91f845d4115f

Exit code: 255

Stdout:''

Stderr: 'Host key verification failed.\ r\ n'

2015-04-22 16 TRACE oslo.messaging.rpc.dispatcher Traceback 2818 22.818 3802 (most recent call last):

The above error indicates that there was an error in executing the following command with the nova user on 117:

Ssh 192.168.10.114 mkdir-p / var/lib/nova/instances/b4d33c9d-c8b1-49e4-9f50-91f845d4115f

Take a look at 117's user file:

Vim / etc/passwd

Among them

Nova:x:162:162:OpenStack Nova Daemons:/var/lib/nova:/sbin/nologin

Please find the linuxpasswd related materials for the specific explanation of the above information.

Modify nova here to be able to log in to the user:

Nova:x:162:162:OpenStack Nova Daemons:/var/lib/nova:/bin/bash

Ssh-keygen-t rsa

Then scp the generated file to the 114node:

Scp / var/lib/nova/.ssh/id_rsa.pub root@192.168.10.114:/var/lib/nova/.ssh/authorized_keys

Then execute under nova: ssh 192.168.10.114

Mistakenly reported that the current account is not available.

Log in to 114 to see:

It was found that the nova user was prohibited from logging in.

Open:

Go to 117 again and find that you can log in:

Note that the group and user of .ssh must be root:root, otherwise login without password will fail

Verify resize again:

Success!

Pay attention to / etc/nova/nova.conf

There are two resize-related configuration items in:

The above indicates that if resize is not confirmed within N seconds after resize, it will automatically resize!

On the ice version of resize error debugging example analysis is shared here, I hope the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.