Re: Creating vm with stemcell failed.... No valid host was found. There are not enough hosts available..Filter ImagePropertiesFilter returned 0 hosts


Tushar Dadlani
 

The new expected behavior is to only allow you to become root if you use
the bosh CLI to perform your ssh since it creates a better audit trails and
prevents unauthorized ssh.

http://bosh.io/jobs/director?source=github.com/cloudfoundry/bosh&version=262.3#p=director.generate_vm_passwords

If the generate_vm_passwords option is set to be true you don't get the
default password on your VM hosts.

Best,
Tushar
On Mon, Jul 17, 2017 at 4:27 AM Arpit Sharma <arpitvipulsharma(a)gmail.com>
wrote:

Hi Johannes,

Today I have tried with other
stemcell(bosh-openstack-kvm-ubuntu-trusty-go_agent-raw). Also created
different security group.I have also mentiond security group rules below.
But still same issue. I am able to login in director with vcap user with
this command
ssh -i /root/.ssh/id_rsa_demokey vcap(a)10.100.10.23

but when I am trying to excute "sudo su -", It is not taking password as
c1oudc0w. I dont know why it is happening.

[root(a)openstack ~(keystone_demo)]# neutron security-group-list

+--------------------------------------+-----------+-----------------------------------------------------------------------------------+
| id | name | security_group_rules
|

+--------------------------------------+-----------+-----------------------------------------------------------------------------------+
| bb412056-6f4e-40d9-a48f-8b1c5c4068eb | boshgroup | egress, IPv4
|
| | | egress, IPv6
|
| | | ingress, IPv4,
1-65535/tcp, remote_group_id: bb412056-6f4e-40d9-a48f-8b1c5c4068eb |
| | | ingress, IPv4,
22/tcp, remote_ip_prefix: 0.0.0.0/0 |
| | | ingress, IPv4,
25555/tcp, remote_ip_prefix: 0.0.0.0/0 |
| | | ingress, IPv4,
6868/tcp, remote_ip_prefix: 0.0.0.0/0 |

Join cf-bosh@lists.cloudfoundry.org to automatically receive all group messages.