-
Notifications
You must be signed in to change notification settings - Fork 0
failed while deploying on AWS #9
Comments
I am a new user of BOSH and I am not sure "parameter groupId is invalid" means which parameter is wrong. The related debug message is this:
|
Can you please paste your sanitized deployment manifest? |
Here it is: <%
director_uuid = '847328c8-6b9c-4ed6-be23-8fb1a997e175'
deployment_name = 'mesos'
num_zookeepers = 3 # Odd number
num_masters = 3 # Odd number
num_marathons = 1
num_chronos = 1
num_jenkins = 1
num_storm = 1
num_slaves = 3
%>
---
name: <%= deployment_name %>
director_uuid: <%= director_uuid %>
releases:
- name: mesos
version: latest
compilation:
workers: 3
network: default
reuse_compilation_vms: true
cloud_properties:
instance_type: m3.xlarge
update:
canaries: 0
canary_watch_time: 30000-60000
update_watch_time: 30000-60000
max_in_flight: 32
serial: false
networks:
- name: default
type: dynamic
cloud_properties:
# subnet: subnet-3c999c48
security_groups:
- mygroup
- <%= deployment_name %>
resource_pools:
- name: default
network: default
stemcell:
name: bosh-aws-xen-ubuntu-trusty-go_agent
version: latest
cloud_properties:
instance_type: m3.medium
- name: slave
network: default
stemcell:
name: bosh-aws-xen-ubuntu-trusty-go_agent
version: latest
cloud_properties:
instance_type: m3.xlarge
jobs:
- name: zookeeper
templates:
- name: zookeeper
instances: <%= num_zookeepers %>
resource_pool: default
persistent_disk: 10240
networks:
- name: default
default: [dns, gateway]
- name: mesos-master
templates:
- name: mesos-master
instances: <%= num_masters %>
resource_pool: default
networks:
- name: default
default: [dns, gateway]
- name: marathon
templates:
- name: marathon
instances: <%= num_marathons %>
resource_pool: default
networks:
- name: default
default: [dns, gateway]
- name: chronos
templates:
- name: chronos
instances: <%= num_chronos %>
resource_pool: default
networks:
- name: default
default: [dns, gateway]
- name: jenkins
templates:
- name: jenkins
instances: <%= num_jenkins %>
resource_pool: default
persistent_disk: 20480
networks:
- name: default
default: [dns, gateway]
- name: storm
templates:
- name: storm
instances: <%= num_storm %>
resource_pool: default
networks:
- name: default
default: [dns, gateway]
- name: mesos-slave
templates:
- name: mesos-slave
instances: <%= num_slaves %>
resource_pool: slave
persistent_disk: 65536
networks:
- name: default
default: [dns, gateway]
properties:
mesos:
principal: "principal"
secret: "secret"
master:
quorum: <%= (num_masters/2) + 1 %>
authenticate_frameworks: true
authenticate_slaves: true
zookeeper:
servers:
<% num_zookeepers.times do |i| %>
<%= "- #{i}.zookeeper.default.#{deployment_name}.microbosh\n" %>
<% end %> |
Basically, I didn't change much.Mainly in the network section: networks:
- name: default
type: dynamic
cloud_properties:
# subnet: subnet-3c999c48
security_groups:
- mygroup
- <%= deployment_name %> The name of my own security group is "mygroup". |
Do you have also a If you don't want to create the |
Yes I have the "mesos" security group, that's why I feel very strange. |
Do those security groups belong to a VPC? If this is the case, you'll need to set the subnet id. If the compilation timeout, it because there's something wrong with the bosh security group. Check this guide about what ports are needed. |
Yes they belong to a VPC.
And I checked vms:
It seems the agents are not responsive and the information of IPs could not be fetched. But actually, I can see all the vms are healthy on the EC2. |
The time outs are usually related to wrong security groups. VM's need to access the bosh director VM to get some metadata. There're several ports involved, but if the new VMs have also the |
We are facing the same error: Director task 75 Started preparing package compilation > Finding packages to compile. Done (00:00:00) Started compiling packages Error 450002: Timed out pinging to 9e960a3c-5fee-4586-9c68-d5c19b014710 after 600 seconds We have opened all the ports on security group, but the issue still persists. |
I installed newest version BOSH ( Version 1.3072.0 (00000000)) on AWS.
I got the following error messages when executing "bosh -n deploy":
The text was updated successfully, but these errors were encountered: