Score:0

Openstack : Instance can't be accessed

cn flag

I installed Openstack Train minimal on centos7 virtualbox host. I can create and run instances but i can't access them via ssh or vnc. The instance is running on provider network. When i was reading the log files i found this. Instance Log

It seems that the instance is leasing IP from Provider Network DHCP server with no errors but can't ping to gateway(192.168.1.1). PS:I used linuxbridge to set up networking and added the ssh and icmp rules on security group.

I also saw this post OpenStack – Instance not respoding but it was done on self service network.

PS: I launched my instance with --config-drive=true option. PS2 : The connectivity to controller and compute node is fine.

Edit 1:

I enabled the ipv4 forwarding on compute node which was turned off but it did not solve the problem. So I deleted the provider network, instance and created the network and instance again. This time no --config-drive options and here is the instance bootup log.

Here is the full log: https://pastebin.com/ywEMgAbq

My guess is instance can't connect with memcached server. (I'm currently working on it)

berndbausch avatar
us flag
Does this router exist in the first place? Does Virtualbox provide connectivity from the instance to this router? Can the instance access other addresses on its network?
Gaaki avatar
cn flag
I used physical router and virtualbox machines connect to it using bridged adapter
berndbausch avatar
us flag
You say "no router", and "I used physical router". This confuses me; is there a router with 192.168.1.1 or is there not? It's weird that the instance gets a reply from the external DHCP server but has no other connectivity to the external network. My first step would be tracing traffic on the VirtualBox bridge and on the Cloud server's external NIC to find out whether the problem is caused by anything outside of the cloud, e.g. VirtualBox, or by the cloud configuration itself.
Gaaki avatar
cn flag
Yea i'm sorry that i confused you.(i thought that i need additional virtual router.) Yeah there is physical router with gateway address of 192.168.1.1. And the connectivity between the router and vm is fine.
berndbausch avatar
us flag
You confuse me again. You say "can't ping to gateway(192.168.1.1)", then "connectivity between the router and vm is fine". If connectivity is fine, which question are you asking?
Gaaki avatar
cn flag
I mean the created instance inside compute node cant ping to gateway. The compute node (the vm) is connected. When i say vm its either control or compute node. And the issue is on the created instance on node.
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.