
OpenStack Nova command errors
Possible cause and recommendationSymptom
You are not specifying anid value
If you run the nova interface-attach <server> command and do not specify the
net-id option, the error Failed to attach interface is displayed even though the
After you execute the
nova
interface-attach
<server> command,
instance is attached to all networks in the project. The OpenStack Compute Service (Nova)
you see a Failed to
also attempts to attach the External Network, which may cause the instance to plug in to the
attach interface
error message
wrong External Network, or may prevent the instance from booting because of a permission
issue.
1. From a Windows or Linux system where the OpenStack CLI package for CloudSystem is
installed, run the nova interface-attach <server> command with at least one of
the following options: net-id, port-id, or fixed-ip.
You are not entering the correct IP address for the instance
You use the nova
sshcommand to
1. Determine the IP address of the instance by viewing the instance details in the CloudSystem
Portal, or by running the nova list command from a Windows or Linux system where
the OpenStack CLI package for CloudSystem is installed.
connect to an instance
and the connection is
made to the Provider
2. Manually ssh to the IP address.
Network instead of the
floating IP address of
the instance
Floating IPs are not working
Possible cause and recommendationSymptom
The instance does not have the proper security rules assigned
You cannot access a
virtual machine
1. Log on to the CloudSystem Portal.
instance over the
External Network
2. From the Project menu in the “Manage Compute” section, select Instances.
using the floating IP 3. On the Instances screen, select the instance.
address associated
with the instance
4. Select More→Edit Security Groups.
5. On the Security Groups tab of the Edit Instance screen, do one of the following
• Choose a security rule that allows you to communicate with the instance.
• Create a new security rule with PuTTY, SSH, or ping access privileges to match your
configuration.
See Create a security group (page 118).
6. Retry accessing the instance.
The instance is connected directly to the External Network
1. Log on to the CloudSystem Portal.
2. From the Project menu in the “Manage Compute” section, select Instances.
3. On the Instances screen, click the link for the instance.
4. On the Instance Overview screen, verify that the instance is connected directly to the External
Network.
5. Delete the instance. See Delete instance (page 109).
6. Relaunch the instance using a provider or private network. See Launching an instance using
CloudSystem Portal (page 119).
7. Associate the private or provider network to the External Network using a logical router.
See Creating an External Network router (page 79).
8. Retry accessing the instance.
The security settings for the Cloud Data Trunk and the External Network port
groups on the ESX management hypervisor are not properly configured
1. Log in to vCenter Server.
2. Select the management hypervisor.
158 Troubleshoot resource configuration
Kommentare zu diesen Handbüchern