CF v202 DEPLOYMENT ON vSPHERE

40 views
Skip to first unread message

Parthiban Annadurai

unread,
Mar 24, 2015, 1:17:34 AM3/24/15
to bosh-...@cloudfoundry.org
Hi All,
         Am trying to deploy CF v202 on vSphere with BOSH version 150 and Ubuntu trusty stemcell version 2865. I had come across so many errors with the help of groups. Now, am struck up with the following error for the past 3 days. Please, anyone help on this issue.. Thanks in Advance..

bosh deploy

Processing deployment manifest
------------------------------
Getting deployment properties from director...
Compiling deployment manifest...
Please review all changes carefully

Deploying
---------
Deployment name: `cf-deployment.yml'
Director name: `bosh'
Are you sure you want to deploy? (type 'yes' to continue): yes

Director task 152
  Started preparing deployment
  Started preparing deployment > Binding deployment. Done (00:00:00)
  Started preparing deployment > Binding releases. Done (00:00:00)
  Started preparing deployment > Binding existing deployment. Done (00:00:00)
  Started preparing deployment > Binding resource pools. Done (00:00:00)
  Started preparing deployment > Binding stemcells. Done (00:00:00)
  Started preparing deployment > Binding templates. Done (00:00:00)
  Started preparing deployment > Binding properties. Done (00:00:00)
  Started preparing deployment > Binding unallocated VMs. Done (00:00:00)
  Started preparing deployment > Binding instance networks. Done (00:00:00)
     Done preparing deployment (00:00:00)

  Started preparing package compilation > Finding packages to compile. Done (00:00:00)

  Started compiling packages
  Started compiling packages > cli/1796b9b4dce96175bcefa60e1afbe1d4b7cd1f6b
  Started compiling packages > loggregator_trafficcontroller/cc2a209b2256500f987001771c0443b48a722780
  Started compiling packages > doppler/f617b689d259f7aa4d4cc5ff81893bf059035ef7
  Started compiling packages > syslog_drain_binder/8c627a89c81b429ea065ca86cf603204ba5eb6af
  Started compiling packages > dea_logging_agent/d0dba8b83454a52ebe60794d13f834243f4c932f
  Started compiling packages > buildpack_cache/4ced0bc62f12dcaa79121718ca3525253ede33b5
   Failed compiling packages > cli/1796b9b4dce96175bcefa60e1afbe1d4b7cd1f6b: undefined method `pop' for nil:NilClass (00:00:07)
   Failed compiling packages > dea_logging_agent/d0dba8b83454a52ebe60794d13f834243f4c932f: undefined method `pop' for nil:NilClass (00:00:07)
   Failed compiling packages > loggregator_trafficcontroller/cc2a209b2256500f987001771c0443b48a722780: undefined method `pop' for nil:NilClass (00:00:10)
   Failed compiling packages > doppler/f617b689d259f7aa4d4cc5ff81893bf059035ef7: undefined method `pop' for nil:NilClass (00:00:10)
   Failed compiling packages > buildpack_cache/4ced0bc62f12dcaa79121718ca3525253ede33b5: undefined method `pop' for nil:NilClass (00:00:10)
   Failed compiling packages > syslog_drain_binder/8c627a89c81b429ea065ca86cf603204ba5eb6af: undefined method `pop' for nil:NilClass (00:00:10)

Error 100: undefined method `pop' for nil:NilClass

Task 152 error

Regards

Parthiban A

Parthiban Annadurai

unread,
Mar 24, 2015, 1:24:05 AM3/24/15
to bosh-...@cloudfoundry.org
My gem list bosh output would be as follows,

gem list bosh

*** LOCAL GEMS ***

bosh-core (1.2859.0)
bosh-director (1.2859.0)
bosh-director-core (1.2865.0, 1.2859.0)
bosh-registry (1.2865.0, 1.2859.0)
bosh-stemcell (1.2865.0, 1.2859.0)
bosh-template (1.2865.0, 1.2859.0)
bosh_aws_cpi (1.2865.0, 1.2859.0)
bosh_cli (1.2865.0, 1.2859.0)
bosh_cli_plugin_micro (1.2865.0, 1.2859.0)
bosh_common (1.2865.0, 1.2859.0)
bosh_cpi (1.2865.0, 1.2859.0)
bosh_openstack_cpi (1.2865.0, 1.2859.0)
bosh_vcloud_cpi (0.7.2)
bosh_vsphere_cpi (1.2865.0, 1.2859.0)


My bosh status would be as follows,

 bosh status
Config
             /root/.bosh_config

Director
  Name       bosh
  Version    1.2865.0 (00000000)
  User       admin
  UUID       68c7f9d5-1d93-43d8-808e-5a66c52e4fb8
  CPI        vsphere
  dns        disabled
  compiled_package_cache disabled
  snapshots  disabled

Deployment
  Manifest   /root/oss/cf-release/cf-deployment.yml

Parthiban Annadurai

unread,
Mar 24, 2015, 8:22:13 AM3/24/15
to bosh-...@cloudfoundry.org
Hi All,
        I have surpassed that above error. The problem was with network related information on manifest file. Thanks All.. Now am struck up with the following error, "Error 450002: Timed out pinging to 4010b034-1bfa-476a-93b3-ad4bc757ce88 after 600 seconds".. if anyone knows, help me on this.. Thanks in Advance..

Parthiban Annadurai

unread,
Mar 24, 2015, 9:39:37 AM3/24/15
to bosh-...@cloudfoundry.org
Hi All,
        The detailed error as follows,

bosh deploy

Processing deployment manifest
------------------------------
Getting deployment properties from director...
Compiling deployment manifest...
Please review all changes carefully

Deploying
---------
Deployment name: `cf-deployment.yml'
Director name: `bosh'
Are you sure you want to deploy? (type 'yes' to continue): yes

Director task 188
  Started preparing deployment
  Started preparing deployment > Binding deployment. Done (00:00:00)
  Started preparing deployment > Binding releases. Done (00:00:00)
  Started preparing deployment > Binding existing deployment. Done (00:00:00)
  Started preparing deployment > Binding resource pools. Done (00:00:00)
  Started preparing deployment > Binding stemcells. Done (00:00:00)
  Started preparing deployment > Binding templates. Done (00:00:00)
  Started preparing deployment > Binding properties. Done (00:00:00)
  Started preparing deployment > Binding unallocated VMs. Done (00:00:00)
  Started preparing deployment > Binding instance networks. Done (00:00:00)
     Done preparing deployment (00:00:00)

  Started preparing package compilation > Finding packages to compile. Done (00:00:01)

  Started compiling packages
  Started compiling packages > cli/1796b9b4dce96175bcefa60e1afbe1d4b7cd1f6b
  Started compiling packages > loggregator_trafficcontroller/cc2a209b2256500f987001771c0443b48a722780
  Started compiling packages > syslog_drain_binder/8c627a89c81b429ea065ca86cf603204ba5eb6af
  Started compiling packages > doppler/f617b689d259f7aa4d4cc5ff81893bf059035ef7
  Started compiling packages > dea_logging_agent/d0dba8b83454a52ebe60794d13f834243f4c932f
  Started compiling packages > buildpack_cache/4ced0bc62f12dcaa79121718ca3525253ede33b5
   Failed compiling packages > syslog_drain_binder/8c627a89c81b429ea065ca86cf603204ba5eb6af: Timed out pinging to 8f939a03-d018-4737-b603-fd97dca2a2ec after 600 seconds (00:10:16)
   Failed compiling packages > cli/1796b9b4dce96175bcefa60e1afbe1d4b7cd1f6b: Timed out pinging to 239dff13-791b-4572-a33a-0152f5963fff after 600 seconds (00:10:16)
   Failed compiling packages > dea_logging_agent/d0dba8b83454a52ebe60794d13f834243f4c932f: Timed out pinging to 6f2d0ad8-a0fd-4411-9af7-5ad36f82581e after 600 seconds (00:10:22)
   Failed compiling packages > loggregator_trafficcontroller/cc2a209b2256500f987001771c0443b48a722780: Timed out pinging to e8857e6c-e8d7-4c95-a275-3aed198df864 after 600 seconds (00:10:22)
   Failed compiling packages > doppler/f617b689d259f7aa4d4cc5ff81893bf059035ef7: Timed out pinging to 9b96ee0e-c1d1-4097-b893-b66931e0c1d9 after 600 seconds (00:10:23)
   Failed compiling packages > buildpack_cache/4ced0bc62f12dcaa79121718ca3525253ede33b5: Timed out pinging to f38e0859-d2fc-45a5-999d-bb617adc1154 after 600 seconds (00:10:24)

Error 450002: Timed out pinging to 8f939a03-d018-4737-b603-fd97dca2a2ec after 600 seconds

Task 188 error

Johannes Hiemer

unread,
Mar 24, 2015, 9:43:11 AM3/24/15
to bosh-...@cloudfoundry.org
Director can't reach the Agents. If the VM is deployed correctly then you should try to Ping the machine. If not able, perhaps there is a firewall in between?

Parthiban Annadurai

unread,
Mar 24, 2015, 9:54:41 AM3/24/15
to bosh-...@cloudfoundry.org
@Johannes.. bosh vms shows the following vms,

bosh vms
Deployment `cf.local'

Director task 189

Task 189 done

+---------------------+---------+---------------+----------------+
| Job/index           | State   | Resource Pool | IPs            |
+---------------------+---------+---------------+----------------+
| ccdb/0              | running | small         | 192.168.33.170 |
| collector/0         | running | small         | 192.168.33.168 |
| debian_nfs_server/0 | running | medium        | 192.168.33.161 |
| login/0             | running | small         | 192.168.33.175 |
| nats/0              | running | small         | 192.168.33.164 |
| postgres_z1/0       | running | small         | 192.168.33.193 |
| services_nfs/0      | running | small         | 192.168.33.162 |
| uaa/0               | running | small         | 192.168.33.174 |
| uaadb/0             | running | small         | 192.168.33.171 |
+---------------------+---------+---------------+----------------+


And am able to ping all the VMs successfully..
Reply all
Reply to author
Forward
0 new messages