Bosh micro deploy stemcell fail


Dimuthu Upeksha
 

Hi,

I'm installing cloud foundry on top openstack and currently I'm following this [1] document to install micro bosh. When I try to deploy a stemcell, I get following issue. I have set security groups as mentioned in the document and I can see that stemcell is running through horizon dashboard. Floating IP and private IP are also attached to the instance but I can't ping to those IPs. What could be the reason for this issue?

[1] http://bosh.io/docs/deploy-microbosh-to-openstack.html

dimuthu(a)dimuthu-H61M-DS2:~/my-micro-deployments$ bosh micro deploy bosh-stemcell-3115-openstack-kvm-centos-7-go_agent.tgz

No `bosh-deployments.yml` file found in current directory.

Conventionally, `bosh-deployments.yml` should be saved in /home/dimuthu.
Is /home/dimuthu/my-micro-deployments a directory where you can save state? (type 'yes' to continue): yes
Deploying new micro BOSH instance `manifest.yml' to `https://192.168.1.228:25555' (type 'yes' to continue): yes

Verifying stemcell...
File exists and readable OK
Verifying tarball...
Read tarball OK
Manifest exists OK
Stemcell image file OK
Stemcell properties OK

Stemcell info
-------------
Name: bosh-openstack-kvm-centos-7-go_agent
Version: 3115

Started deploy micro bosh
Started deploy micro bosh > Unpacking stemcell. Done (00:00:05)
Started deploy micro bosh > Uploading stemcell. Done (00:00:18)
Started deploy micro bosh > Creating VM from bb248d4f-dbf2-4814-a516-f4344acc1589. Done (00:00:47)
Started deploy micro bosh > Waiting for the agent


log writing failed. can't be called from trap context
/usr/local/lib/ruby/gems/2.2.0/gems/net-ssh-2.9.2/lib/net/ssh/transport/session.rb:70:in `initialize': No route to host - connect(2) for "192.168.1.228" port 22 (Errno::EHOSTUNREACH)
from /usr/local/lib/ruby/gems/2.2.0/gems/net-ssh-2.9.2/lib/net/ssh/transport/session.rb:70:in `open'
from /usr/local/lib/ruby/gems/2.2.0/gems/net-ssh-2.9.2/lib/net/ssh/transport/session.rb:70:in `block in initialize'
from /usr/local/lib/ruby/2.2.0/timeout.rb:73:in `timeout'
from /usr/local/lib/ruby/2.2.0/timeout.rb:124:in `timeout'
from /usr/local/lib/ruby/gems/2.2.0/gems/net-ssh-2.9.2/lib/net/ssh/transport/session.rb:67:in `initialize'
from /usr/local/lib/ruby/gems/2.2.0/gems/net-ssh-2.9.2/lib/net/ssh.rb:207:in `new'
from /usr/local/lib/ruby/gems/2.2.0/gems/net-ssh-2.9.2/lib/net/ssh.rb:207:in `start'
from /usr/local/lib/ruby/gems/2.2.0/gems/bosh_cli_plugin_micro-1.3115.0/lib/bosh/deployer/ssh_server.rb:37:in `start_session'
from /usr/local/lib/ruby/gems/2.2.0/gems/bosh_cli_plugin_micro-1.3115.0/lib/bosh/deployer/remote_tunnel.rb:20:in `block in create'
from /usr/local/lib/ruby/gems/2.2.0/gems/bosh_cli_plugin_micro-1.3115.0/lib/bosh/deployer/remote_tunnel.rb:19:in `loop'
from /usr/local/lib/ruby/gems/2.2.0/gems/bosh_cli_plugin_micro-1.3115.0/lib/bosh/deployer/remote_tunnel.rb:19:in `create'
from /usr/local/lib/ruby/gems/2.2.0/gems/bosh_cli_plugin_micro-1.3115.0/lib/bosh/deployer/instance_manager/openstack.rb:28:in `remote_tunnel'
from /usr/local/lib/ruby/gems/2.2.0/gems/bosh_cli_plugin_micro-1.3115.0/lib/bosh/deployer/instance_manager.rb:452:in `wait_until_agent_ready'
from /usr/local/lib/ruby/gems/2.2.0/gems/bosh_cli_plugin_micro-1.3115.0/lib/bosh/deployer/instance_manager.rb:130:in `block in create'
from /usr/local/lib/ruby/gems/2.2.0/gems/bosh_cli_plugin_micro-1.3115.0/lib/bosh/deployer/instance_manager.rb:85:in `step'
from /usr/local/lib/ruby/gems/2.2.0/gems/bosh_cli_plugin_micro-1.3115.0/lib/bosh/deployer/instance_manager.rb:128:in `create'
from /usr/local/lib/ruby/gems/2.2.0/gems/bosh_cli_plugin_micro-1.3115.0/lib/bosh/deployer/instance_manager.rb:98:in `block in create_deployment'
from /usr/local/lib/ruby/gems/2.2.0/gems/bosh_cli_plugin_micro-1.3115.0/lib/bosh/deployer/instance_manager.rb:92:in `with_lifecycle'
from /usr/local/lib/ruby/gems/2.2.0/gems/bosh_cli_plugin_micro-1.3115.0/lib/bosh/deployer/instance_manager.rb:98:in `create_deployment'
from /usr/local/lib/ruby/gems/2.2.0/gems/bosh_cli_plugin_micro-1.3115.0/lib/bosh/cli/commands/micro.rb:179:in `perform'
from /usr/local/lib/ruby/gems/2.2.0/gems/bosh_cli-1.3115.0/lib/cli/command_handler.rb:57:in `run'
from /usr/local/lib/ruby/gems/2.2.0/gems/bosh_cli-1.3115.0/lib/cli/runner.rb:56:in `run'
from /usr/local/lib/ruby/gems/2.2.0/gems/bosh_cli-1.3115.0/bin/bosh:19:in `<top (required)>'
from /usr/local/bin/bosh:23:in `load'
from /usr/local/bin/bosh:23:in `<main>'


Marco Voelz
 

Dear Dimuthu,

bosh micro is deprecated. If you are starting out with a fresh installation of bosh, please use bosh-init [1] instead.

That being said, if you want to continue the path for `bosh micro`: it seems that you the IP 192.168.1.228 in your logs is a local IP and not a floating IP. I guess the machine you are running the `bosh micro deploy` command from has no access to that local IP address. Please make sure that `network.vip` contains a floating IP in your deployment manifest.

Additionally it seems that port 22 is missing in the table in the bosh.io documentation for bosh micro [2]. So please add a rule for Ingress IPv4 TCP on port 22 from IP 0.0.0.0/0 (CIDR) to your bosh security group.

Warm regards
Marco

[1] http://bosh.io/docs/init-openstack.html
[2] http://bosh.io/docs/deploy-microbosh-to-openstack.html#security-groups


Bharath
 

Hi Dimuthu,

It seems you are having issue with openstack here . please check your
openstack security groups . Can you tell which networking project are you
using nova or neutron ?

regards
Bharath

On Wed, Nov 4, 2015 at 11:49 PM, Voelz, Marco <marco.voelz(a)sap.com> wrote:

Dear Dimuthu,

bosh micro is deprecated. If you are starting out with a fresh
installation of bosh, please use bosh-init [1] instead.

That being said, if you want to continue the path for `bosh micro`: it
seems that you the IP 192.168.1.228 in your logs is a local IP and not a
floating IP. I guess the machine you are running the `bosh micro deploy`
command from has no access to that local IP address. Please make sure that
`network.vip` contains a floating IP in your deployment manifest.

Additionally it seems that port 22 is missing in the table in the bosh.io
documentation for bosh micro [2]. So please add a rule for Ingress IPv4 TCP
on port 22 from IP 0.0.0.0/0 (CIDR) to your bosh security group.

Warm regards
Marco

[1] http://bosh.io/docs/init-openstack.html
[2] http://bosh.io/docs/deploy-microbosh-to-openstack.html#security-groups


Dimuthu Upeksha
 

Hi Marco,

Many thanks for the reply.

I added IPv4 TCP rule for port 22 but I still get above error. I have two networks. 10.0.0.0/24 is the private network and 192.168.1.0/24 is the public network.

Thanks
Dimuthu


Dimuthu Upeksha
 

Hi Bharath,

I double checked my security groups. I use neutron as the networking part in OpenStack.

Thanks,
Dimuthu


Marco Voelz
 

Dear Dimuthu,

please make sure that your OpenStack environment is configured correctly and that you can access any machine booted up with a floating IP from your machine. You can follow the description in the Cloud Foundry documentation [1] to verify this.

Warm regards
Marco





[1] http://docs.cloudfoundry.org/deploying/openstack/validate_openstack.html#internal-external-ips


Dimuthu Upeksha
 

Hi Marko,

I verified that and I can ping to the floating IPs which I assigned for cirros instances. However I was trying with CentOS stemcell. Now I tried it with Ubuntu stemcell and now I can successfully finish the installation. I guess there is a permission issue in CentOS stemcell.

Thanks
Dimuthu


Bharath
 

Hi Dimuthu,,

can you provide the screen shots of your security groups . I also want to
see each security group rules .

regards
Bharath

On Fri, Nov 6, 2015 at 3:25 PM, Dimuthu Upeksha <dimuthu(a)adroitlogic.com>
wrote:

Hi Marko,

I verified that and I can ping to the floating IPs which I assigned for
cirros instances. However I was trying with CentOS stemcell. Now I tried it
with Ubuntu stemcell and now I can successfully finish the installation. I
guess there is a permission issue in CentOS stemcell.

Thanks
Dimuthu


Dimuthu Upeksha