Ask Your Question
0

Cannot access instance

asked 2013-09-29 07:57:59 -0600

Himanshu gravatar image

I have setup cloud using docs.openstack.org documenation on RHEL 6.3. The problem is I cannot access the instance from controller node. I have only one NIC named p2p1 and I have setup bridge br0 for it.

The controller and compute node are on same machine.

I cannot ping or ssh to the instance nor the dashboard console is working (it says an error occurred . please try again later).

I have enabled icmp and ssh in default security group and I am only using nova not quantum.

My nova.conf file is

[

DEFAULT]
logdir = /var/log/nova
state_path = /var/lib/nova
lock_path = /var/lib/nova/tmp
volumes_dir = /etc/nova/volumes
dhcpbridge = /usr/bin/nova-dhcpbridge
dhcpbridge_flagfile = /etc/nova/nova.conf
force_dhcp_release = True
injected_network_template = /usr/share/nova/interfaces.template
libvirt_nonblocking = True
libvirt_inject_partition = -1
libvirt_type = kvm
network_manager = nova.network.manager.FlatDHCPManager
iscsi_helper = tgtadm
sql_connection = mysql://nova:nova@192.168.1.130/nova
compute_driver = libvirt.LibvirtDriver
firewall_driver = nova.virt.libvirt.firewall.IptablesFirewallDriver
rpc_backend = nova.openstack.common.rpc.impl_qpid
qpid_hostname = 192.168.1.130
rootwrap_config = /etc/nova/rootwrap.conf
auth_strategy = keystone
verbose = True

#SCHEDULER
compute_scheduler_driver = nova.scheduler.filter_scheduler.FilterScheduler

#VOLUMES
volume_api_class = nova.volume.cinder.API
volume_driver = nova.volume.driver.ISCSIDriver
volume_group = cinder-volumes
volume_name_template = volume-%s

#COMPUTE
compute_driver = libvirt.LibvirtDriver
instance_name_template = instance-%08x
api_paste_config = /etc/nova/api-paste.ini

#allow_resize_to_same_host = True

# APIS
osapi_compute_extension = nova.api.openstack.compute.contrib.standard_extensions
ec2_dmz_host = 192.168.1.130
s3_host = 192.168.1.130
enabled_apis = ec2,osapi_compute,metadata


# GLANCE
image_service=nova.image.glance.GlanceImageService
glance_api_servers = 192.168.1.130:9292

# NETWORK
force_dhcp_release = True
dhcpbridge_flagfile = /etc/nova/nova.conf
firewall_driver = nova.virt.libvirt.firewall.IptablesFirewallDriver
# Change my_ip to match each host
my_ip = 192.168.1.130
public_interface = p2p1
vlan_interface = p2p1
flat_network_bridge = br0
flat_interface = p2p1
fixed_range = 192.168.1.0/24

# NOVNC CONSOLE
novncproxy_base_url = http://192.168.1.130:6080/vnc_auto.html
# Change vncserver_proxyclient_address and vncserver_listen to match each compute host
vncserver_proxyclient_address = 192.168.1.130
vncserver_listen = 0.0.0.0

[keystone_authtoken]
admin_tenant_name = service
admin_user = nova
admin_password = nova
auth_host = 192.168.1.130
auth_port = 35357
auth_protocol = http
signing_dir = /tmp/keystone-signing-nova

* The instance log is as follows *

[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 3.2.0-37-virtual (buildd@allspice) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #58-Ubuntu SMP Thu Jan 24 15:48:03 UTC 2013 (Ubuntu 3.2.0-37.58-virtual 3.2.35)
[    0.000000] Command line: LABEL=cirros-rootfs ro console=tty1 console=ttyS0
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Centaur CentaurHauls
[    0.000000] Disabled fast string operations
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  BIOS-e820: 0000000000000000 - 000000000009dc00 (usable)
[    0.000000]  BIOS-e820: 000000000009dc00 - 00000000000a0000 (reserved)
[    0.000000]  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[    0.000000]  BIOS-e820: 0000000000100000 - 000000007fffd000 (usable)
[    0.000000]  BIOS-e820: 000000007fffd000 - 0000000080000000 (reserved)
[    0.000000]  BIOS-e820: 00000000fffbc000 - 0000000100000000 (reserved)
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] DMI 2.4 present.
[    0.000000] No AGP bridge found
[    0.000000] last_pfn = 0x7fffd max_arch_pfn = 0x400000000
[    0.000000] x86 PAT enabled: cpu ...
(more)
edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2013-12-06 01:18:10 -0600

Kunal Patil gravatar image

Do you still have this problem?

When I had a similar error, I tried stopping iptables on both Controller and Compute node. It made the problem disappear. Later, I used RDO packstack to install Controller and Compute nodes, which creates appropriate iptables rules for access to various Openstack components.

service iptables stop

If this does not work, try disabling selinux in the file /etc/sysconfig/selinux.

edit flag offensive delete link more

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: 2013-09-29 07:57:59 -0600

Seen: 635 times

Last updated: Dec 06 '13