Solution to problems that nova-compute and nova-volume cannot start after OpenStackNova is installed on deletuserver12.04

When building OpenStack, many people will refer to the example and steps on "OS-compute-startguide-trunk" and select Ubuntuserver12.04 for installation. The above steps must be correct, but because the documents cannot be all-encompassing and the system settings will not be identical, errors are inevitable during the installation process. Run sudonova-manageservicelis

When building OpenStack, many people will refer to the example and steps on "OS-compute-startguide-trunk" and select Ubuntu server 12.04 for installation. The above steps must be correct, but because the documents cannot be all-encompassing and the system settings will not be identical, errors are inevitable during the installation process.

After the installation is completed in the Nova step, run the sudo nova-manage service list. Two services are not started: nova-volume and nova-compute.

After an error occurs, I picked up the logs of nova-volume and nova-compute under/var/log/nova/respectively, and found that there was almost no valid error message.

Then, after continuing to view the long OpenStack Compute Administration Manual document, I finally learned why.

1. The reason for the failure of the nova-compute operation: the/etc/nova. conf configuration file is incorrect.

This is almost undisputed. Maybe you configure it according to the above instructions, but in the example above, the management node has two NICs, one of which serves as a bridge. If it is configured based on your actual machine and network environment, nova-compute will not run normally. You can replace it with the default configuration file and start it again.

2. Why does nova-volume fail to run properly: you do not have a volume group named nova-volumes)

Of course there are many reasons for this, but if you install nova on Ubuntu server 12.04, there is a small trap. During Operating System installation, the default volume group VG name is your server name. It is estimated that you will not name it like nova-nolumes during installation. The solution is to rename VG:

Vgrename: Rename a volume group
Vgrename
[-A | -- autobackup y | n]
[-D | -- debug]
[-H | -- help]
[-T | -- test]
[-V | -- verbose]
[-- Version]
OldVolumeGroupPath NewVolumeGroupPath |
OldVolumeGroupName NewVolumeGroupName

You only need vgrename OldVolumeGroupName nova-volumes!

For more information about Ubuntu, see Ubuntu special page http://www.linuxidc.com/topicnews.aspx? Tid = 2