Date
1 - 9 of 9
cloudfoundry-incubator / diego-release deploy failing
|
Shetty, Daya <Daya.Shetty@...>
I¹m getting errors while deploying the diego release..
BOSH version 1.3012.0 CF release 212. Bosh Diego release 0.1367 $ bosh deployment ~/deployments/bosh-lite/cf.yml Deployment set to `/Users/xbbly9r/deployments/bosh-lite/cf.yml' $ bosh -n deploy ŠŠŠ Done binding instance vms > postgres_z1/0 (00:00:00) Done binding instance vms > consul_z1/0 (00:00:00) Done binding instance vms > nats_z1/0 (00:00:00) Done binding instance vms > etcd_z1/0 (00:00:00) Done binding instance vms > ha_proxy_z1/0 (00:00:00) Done binding instance vms > uaa_z1/0 (00:00:00) Done binding instance vms > hm9000_z1/0 (00:00:00) Done binding instance vms > api_z1/0 (00:00:00) Done binding instance vms > router_z1/0 (00:00:00) Done binding instance vms > runner_z1/0 (00:00:00) Done binding instance vms > loggregator_trafficcontroller_z1/0 (00:00:00) Done binding instance vms > doppler_z1/0 (00:00:00) Done binding instance vms (00:00:00) Started preparing configuration > Binding configuration. Failed: Error filling in template `agent_ctl.sh.erb' for `uaa_z1/0' (line 31: undefined method `tr' for ["uaa", {}]:Array) (00:00:01) Error 100: Error filling in template `agent_ctl.sh.erb' for `uaa_z1/0' (line 31: undefined method `tr' for ["uaa", {}]:Array) $ bosh deployment ~/deployments/bosh-lite/diego.yml Deployment set to `/Users/xbbly9r/deployments/bosh-lite/diego.yml¹ Š. 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 preparing dns > Binding DNS. Done (00:00:00) Started preparing configuration > Binding configuration. Failed: Error filling in template `agent_ctl.sh.erb' for `database_z1/0' (line 31: undefined method `tr' for ["bbs", {}]:Array) (00:00:00) Error 100: Error filling in template `agent_ctl.sh.erb' for `database_z1/0' (line 31: undefined method `tr' for ["bbs", {}]:Array) Any ideas on what I can do to resolve these issues? Regards Daya PS: I have attached the debug logs for both the errors. The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. |
|
|
|
Eric Malm <emalm@...>
Hi, Daya,
It looks like the consul service data in your deployment manifests is incompatible with the data that the consul agent job expects to consume in its agent_ctl.sh.erb script template. These data structures did change after CF v212 was released, in this cf-release commit <https://github.com/cloudfoundry/cf-release/commit/929aae4a2b6c6de20d48341c18bbe20b33bc432d>. If you're indeed deploying CF final version 212, the release notes for that version <https://github.com/cloudfoundry/cf-release/releases/tag/v212> recommend you deploy Diego final version 0.1304.0 alongside it. As long as you generate your deployment manifests from the commits for those final releases, it should have the consul service data in the correct format for the consul agent job. Thanks, Eric, CF Runtime Diego PM On Mon, Jul 13, 2015 at 3:29 PM, Shetty, Daya <Daya.Shetty(a)bnymellon.com> wrote: I¹m getting errors while deploying the diego release.. |
|
|
|
Shetty, Daya <Daya.Shetty@...>
Hi Eric,
toggle quoted message
Show quoted text
Thanks for responding, as far as I can tell, I did generate the deployment manifest correctly. But just to make sure I deleted the deployment and my cf-release repo and redid the whole process, currently uploading the cf-213.yml and will then deploy this version to see whether it syncs up the consul agent correctly. This time I’m following the steps mentioned in https://github.com/cloudfoundry/bosh-lite/blob/develop/docs/deploy-cf.md instead of the steps mentioned in https://github.com/cloudfoundry-incubator/diego-release. Will update you of any problems once I’m done deploying. Regards Daya From: <cf-bosh-bounces(a)lists.cloudfoundry.org<mailto:cf-bosh-bounces(a)lists.cloudfoundry.org>> on behalf of Eric Malm <emalm(a)pivotal.io<mailto:emalm(a)pivotal.io>> Reply-To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Date: Tuesday, July 14, 2015 at 3:39 PM To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Subject: Re: [cf-bosh] cloudfoundry-incubator / diego-release deploy failing Hi, Daya, It looks like the consul service data in your deployment manifests is incompatible with the data that the consul agent job expects to consume in its agent_ctl.sh.erb script template. These data structures did change after CF v212 was released, in this cf-release commit<https://github.com/cloudfoundry/cf-release/commit/929aae4a2b6c6de20d48341c18bbe20b33bc432d>. If you're indeed deploying CF final version 212, the release notes for that version<https://github.com/cloudfoundry/cf-release/releases/tag/v212> recommend you deploy Diego final version 0.1304.0 alongside it. As long as you generate your deployment manifests from the commits for those final releases, it should have the consul service data in the correct format for the consul agent job. Thanks, Eric, CF Runtime Diego PM On Mon, Jul 13, 2015 at 3:29 PM, Shetty, Daya <Daya.Shetty(a)bnymellon.com<mailto:Daya.Shetty(a)bnymellon.com>> wrote:
I¹m getting errors while deploying the diego release.. BOSH version 1.3012.0 CF release 212. Bosh Diego release 0.1367 $ bosh deployment ~/deployments/bosh-lite/cf.yml Deployment set to `/Users/xbbly9r/deployments/bosh-lite/cf.yml' $ bosh -n deploy ŠŠŠ Done binding instance vms > postgres_z1/0 (00:00:00) Done binding instance vms > consul_z1/0 (00:00:00) Done binding instance vms > nats_z1/0 (00:00:00) Done binding instance vms > etcd_z1/0 (00:00:00) Done binding instance vms > ha_proxy_z1/0 (00:00:00) Done binding instance vms > uaa_z1/0 (00:00:00) Done binding instance vms > hm9000_z1/0 (00:00:00) Done binding instance vms > api_z1/0 (00:00:00) Done binding instance vms > router_z1/0 (00:00:00) Done binding instance vms > runner_z1/0 (00:00:00) Done binding instance vms > loggregator_trafficcontroller_z1/0 (00:00:00) Done binding instance vms > doppler_z1/0 (00:00:00) Done binding instance vms (00:00:00) Started preparing configuration > Binding configuration. Failed: Error filling in template `agent_ctl.sh.erb' for `uaa_z1/0' (line 31: undefined method `tr' for ["uaa", {}]:Array) (00:00:01) Error 100: Error filling in template `agent_ctl.sh.erb' for `uaa_z1/0' (line 31: undefined method `tr' for ["uaa", {}]:Array) $ bosh deployment ~/deployments/bosh-lite/diego.yml Deployment set to `/Users/xbbly9r/deployments/bosh-lite/diego.yml¹ Š. 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 preparing dns > Binding DNS. Done (00:00:00) Started preparing configuration > Binding configuration. Failed: Error filling in template `agent_ctl.sh.erb' for `database_z1/0' (line 31: undefined method `tr' for ["bbs", {}]:Array) (00:00:00) Error 100: Error filling in template `agent_ctl.sh.erb' for `database_z1/0' (line 31: undefined method `tr' for ["bbs", {}]:Array) Any ideas on what I can do to resolve these issues? Regards Daya PS: I have attached the debug logs for both the errors. The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org> https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. |
|
|
|
Eric Malm <emalm@...>
Hi, Daya,
Good luck with the refreshed deployment! Please do note that CF v213 was not recommended for general use, as it contained a CCDB migration that was not backwards compatible. For a new deployment, though, it may be fine. The recommended compatible version of Diego is 0.1353.0. The consul agent job in CF v213 uses the new consul service data format that allows tags to be specified for each registered service. If the jobs in your deployment manifests have consul.agent.services properties with entries of the form uaa: {}, the manifests should be configured correctly. If the entries have the form - uaa, it's the old format, which won't work for the newer version of the consul agent script template. Best, Eric On Tue, Jul 14, 2015 at 6:26 PM, Shetty, Daya <Daya.Shetty(a)bnymellon.com> wrote: Hi Eric, |
|
|
|
Shetty, Daya <Daya.Shetty@...>
Hi Eric,
toggle quoted message
Show quoted text
I have successfully deployed the Diego release as per the recommended compatible versions you mentioned, but now hitting the next road block while executing “cf api” commands. Also I have attached the deployed release details in a separate file. Any ideas what I can do to resolve this issue? Here are the details regarding the failure: diego-release $ cf api --skip-ssl-validation api.10.244.0.34.xip.io Setting api endpoint to api.10.244.0.34.xip.io... FAILED Error performing request: Get http://api.10.244.0.34.xip.io/v2/info: dial tcp 10.244.0.34:80: can't assign requested address :diego-release $ route get 10.244.0.34.xip.io route to: 10.244.0.34 destination: 10.244.0.34 gateway: 192.168.50.4 interface: en0 flags: <UP,GATEWAY,HOST,DONE,WASCLONED,IFSCOPE,IFREF> recvpipe sendpipe ssthresh rtt,msec rttvar hopcount mtu expire 0 0 0 0 0 0 1500 0 :diego-release $ ping 192.168.50.4 PING 192.168.50.4 (192.168.50.4): 56 data bytes 64 bytes from 192.168.50.4: icmp_seq=0 ttl=64 time=0.340 ms 64 bytes from 192.168.50.4: icmp_seq=1 ttl=64 time=0.304 ms --- 192.168.50.4 ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.304/0.322/0.340/0.018 ms :diego-release $ Thanks in advance, Regards Daya From: <cf-bosh-bounces(a)lists.cloudfoundry.org<mailto:cf-bosh-bounces(a)lists.cloudfoundry.org>> on behalf of Eric Malm <emalm(a)pivotal.io<mailto:emalm(a)pivotal.io>> Reply-To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Date: Tuesday, July 14, 2015 at 7:01 PM To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Subject: Re: [cf-bosh] cloudfoundry-incubator / diego-release deploy failing Hi, Daya, Good luck with the refreshed deployment! Please do note that CF v213 was not recommended for general use, as it contained a CCDB migration that was not backwards compatible. For a new deployment, though, it may be fine. The recommended compatible version of Diego is 0.1353.0. The consul agent job in CF v213 uses the new consul service data format that allows tags to be specified for each registered service. If the jobs in your deployment manifests have consul.agent.services properties with entries of the form uaa: {}, the manifests should be configured correctly. If the entries have the form - uaa, it's the old format, which won't work for the newer version of the consul agent script template. Best, Eric On Tue, Jul 14, 2015 at 6:26 PM, Shetty, Daya <Daya.Shetty(a)bnymellon.com<mailto:Daya.Shetty(a)bnymellon.com>> wrote:
Hi Eric, Thanks for responding, as far as I can tell, I did generate the deployment manifest correctly. But just to make sure I deleted the deployment and my cf-release repo and redid the whole process, currently uploading the cf-213.yml and will then deploy this version to see whether it syncs up the consul agent correctly. This time I’m following the steps mentioned in https://github.com/cloudfoundry/bosh-lite/blob/develop/docs/deploy-cf.md instead of the steps mentioned in https://github.com/cloudfoundry-incubator/diego-release. Will update you of any problems once I’m done deploying. Regards Daya From: <cf-bosh-bounces(a)lists.cloudfoundry.org<mailto:cf-bosh-bounces(a)lists.cloudfoundry.org>> on behalf of Eric Malm <emalm(a)pivotal.io<mailto:emalm(a)pivotal.io>> Reply-To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Date: Tuesday, July 14, 2015 at 3:39 PM To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Subject: Re: [cf-bosh] cloudfoundry-incubator / diego-release deploy failing Hi, Daya, It looks like the consul service data in your deployment manifests is incompatible with the data that the consul agent job expects to consume in its agent_ctl.sh.erb script template. These data structures did change after CF v212 was released, in this cf-release commit<https://github.com/cloudfoundry/cf-release/commit/929aae4a2b6c6de20d48341c18bbe20b33bc432d>. If you're indeed deploying CF final version 212, the release notes for that version<https://github.com/cloudfoundry/cf-release/releases/tag/v212> recommend you deploy Diego final version 0.1304.0 alongside it. As long as you generate your deployment manifests from the commits for those final releases, it should have the consul service data in the correct format for the consul agent job. Thanks, Eric, CF Runtime Diego PM On Mon, Jul 13, 2015 at 3:29 PM, Shetty, Daya <Daya.Shetty(a)bnymellon.com<mailto:Daya.Shetty(a)bnymellon.com>> wrote: I¹m getting errors while deploying the diego release.. BOSH version 1.3012.0 CF release 212. Bosh Diego release 0.1367 $ bosh deployment ~/deployments/bosh-lite/cf.yml Deployment set to `/Users/xbbly9r/deployments/bosh-lite/cf.yml' $ bosh -n deploy ŠŠŠ Done binding instance vms > postgres_z1/0 (00:00:00) Done binding instance vms > consul_z1/0 (00:00:00) Done binding instance vms > nats_z1/0 (00:00:00) Done binding instance vms > etcd_z1/0 (00:00:00) Done binding instance vms > ha_proxy_z1/0 (00:00:00) Done binding instance vms > uaa_z1/0 (00:00:00) Done binding instance vms > hm9000_z1/0 (00:00:00) Done binding instance vms > api_z1/0 (00:00:00) Done binding instance vms > router_z1/0 (00:00:00) Done binding instance vms > runner_z1/0 (00:00:00) Done binding instance vms > loggregator_trafficcontroller_z1/0 (00:00:00) Done binding instance vms > doppler_z1/0 (00:00:00) Done binding instance vms (00:00:00) Started preparing configuration > Binding configuration. Failed: Error filling in template `agent_ctl.sh.erb' for `uaa_z1/0' (line 31: undefined method `tr' for ["uaa", {}]:Array) (00:00:01) Error 100: Error filling in template `agent_ctl.sh.erb' for `uaa_z1/0' (line 31: undefined method `tr' for ["uaa", {}]:Array) $ bosh deployment ~/deployments/bosh-lite/diego.yml Deployment set to `/Users/xbbly9r/deployments/bosh-lite/diego.yml¹ Š. 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 preparing dns > Binding DNS. Done (00:00:00) Started preparing configuration > Binding configuration. Failed: Error filling in template `agent_ctl.sh.erb' for `database_z1/0' (line 31: undefined method `tr' for ["bbs", {}]:Array) (00:00:00) Error 100: Error filling in template `agent_ctl.sh.erb' for `database_z1/0' (line 31: undefined method `tr' for ["bbs", {}]:Array) Any ideas on what I can do to resolve these issues? Regards Daya PS: I have attached the debug logs for both the errors. The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org> https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org> https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. |
|
|
|
Eric Malm <emalm@...>
Hi, Daya,
Hmm, that sounds like something strange with the local networking on your machine. The 'can't assign requested address' error is coming from the Golang standard networking libraries, and may indicate that it's unable to allocate an ephemeral port for the connection to the target address. From your 'route' command output, it does look like you're correctly using the bosh-lite VM as your gateway. Are you able to run 'curl http://api.10.244.0.34.xip.io/v2/info' directly? Thanks, Eric On Wed, Jul 15, 2015 at 4:40 PM, Shetty, Daya <Daya.Shetty(a)bnymellon.com> wrote: Hi Eric, |
|
|
|
Shetty, Daya <Daya.Shetty@...>
Hi Eric,
toggle quoted message
Show quoted text
Agree, It has stumped me too, hence asking the list if anyone has seen this behavior. Logging into the bosh-lite VM I can run the cf commands fine but not from my MAC. Also tried curl & telnet to port 80 and both return errors so ruling out CF cli issue on Mac OS. curl http://api.10.244.0.34.xip.io/v2/info curl: (7) Couldn't connect to server $ telnet 10.244.0.34 80 Trying 10.244.0.34... telnet: connect to address 10.244.0.34: Can't assign requested address telnet: Unable to connect to remote host Thanks Daya From: <cf-bosh-bounces(a)lists.cloudfoundry.org<mailto:cf-bosh-bounces(a)lists.cloudfoundry.org>> on behalf of Eric Malm <emalm(a)pivotal.io<mailto:emalm(a)pivotal.io>> Reply-To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Date: Thursday, July 16, 2015 at 8:57 AM To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Subject: Re: [cf-bosh] cloudfoundry-incubator / diego-release deploy failing Hi, Daya, Hmm, that sounds like something strange with the local networking on your machine. The 'can't assign requested address' error is coming from the Golang standard networking libraries, and may indicate that it's unable to allocate an ephemeral port for the connection to the target address. From your 'route' command output, it does look like you're correctly using the bosh-lite VM as your gateway. Are you able to run 'curl http://api.10.244.0.34.xip.io/v2/info' directly? Thanks, Eric On Wed, Jul 15, 2015 at 4:40 PM, Shetty, Daya <Daya.Shetty(a)bnymellon.com<mailto:Daya.Shetty(a)bnymellon.com>> wrote:
Hi Eric, I have successfully deployed the Diego release as per the recommended compatible versions you mentioned, but now hitting the next road block while executing “cf api” commands. Also I have attached the deployed release details in a separate file. Any ideas what I can do to resolve this issue? Here are the details regarding the failure: diego-release $ cf api --skip-ssl-validation api.10.244.0.34.xip.io<http://api.10.244.0.34.xip.io> Setting api endpoint to api.10.244.0.34.xip.io<http://api.10.244.0.34.xip.io>... FAILED Error performing request: Get http://api.10.244.0.34.xip.io/v2/info: dial tcp 10.244.0.34:80<http://10.244.0.34:80>: can't assign requested address :diego-release $ route get 10.244.0.34.xip.io<http://10.244.0.34.xip.io> route to: 10.244.0.34 destination: 10.244.0.34 gateway: 192.168.50.4 interface: en0 flags: <UP,GATEWAY,HOST,DONE,WASCLONED,IFSCOPE,IFREF> recvpipe sendpipe ssthresh rtt,msec rttvar hopcount mtu expire 0 0 0 0 0 0 1500 0 :diego-release $ ping 192.168.50.4 PING 192.168.50.4 (192.168.50.4): 56 data bytes 64 bytes from 192.168.50.4<http://192.168.50.4>: icmp_seq=0 ttl=64 time=0.340 ms 64 bytes from 192.168.50.4<http://192.168.50.4>: icmp_seq=1 ttl=64 time=0.304 ms --- 192.168.50.4 ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.304/0.322/0.340/0.018 ms :diego-release $ Thanks in advance, Regards Daya From: <cf-bosh-bounces(a)lists.cloudfoundry.org<mailto:cf-bosh-bounces(a)lists.cloudfoundry.org>> on behalf of Eric Malm <emalm(a)pivotal.io<mailto:emalm(a)pivotal.io>> Reply-To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Date: Tuesday, July 14, 2015 at 7:01 PM To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Subject: Re: [cf-bosh] cloudfoundry-incubator / diego-release deploy failing Hi, Daya, Good luck with the refreshed deployment! Please do note that CF v213 was not recommended for general use, as it contained a CCDB migration that was not backwards compatible. For a new deployment, though, it may be fine. The recommended compatible version of Diego is 0.1353.0. The consul agent job in CF v213 uses the new consul service data format that allows tags to be specified for each registered service. If the jobs in your deployment manifests have consul.agent.services properties with entries of the form uaa: {}, the manifests should be configured correctly. If the entries have the form - uaa, it's the old format, which won't work for the newer version of the consul agent script template. Best, Eric On Tue, Jul 14, 2015 at 6:26 PM, Shetty, Daya <Daya.Shetty(a)bnymellon.com<mailto:Daya.Shetty(a)bnymellon.com>> wrote: Hi Eric, Thanks for responding, as far as I can tell, I did generate the deployment manifest correctly. But just to make sure I deleted the deployment and my cf-release repo and redid the whole process, currently uploading the cf-213.yml and will then deploy this version to see whether it syncs up the consul agent correctly. This time I’m following the steps mentioned in https://github.com/cloudfoundry/bosh-lite/blob/develop/docs/deploy-cf.md instead of the steps mentioned in https://github.com/cloudfoundry-incubator/diego-release. Will update you of any problems once I’m done deploying. Regards Daya From: <cf-bosh-bounces(a)lists.cloudfoundry.org<mailto:cf-bosh-bounces(a)lists.cloudfoundry.org>> on behalf of Eric Malm <emalm(a)pivotal.io<mailto:emalm(a)pivotal.io>> Reply-To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Date: Tuesday, July 14, 2015 at 3:39 PM To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Subject: Re: [cf-bosh] cloudfoundry-incubator / diego-release deploy failing Hi, Daya, It looks like the consul service data in your deployment manifests is incompatible with the data that the consul agent job expects to consume in its agent_ctl.sh.erb script template. These data structures did change after CF v212 was released, in this cf-release commit<https://github.com/cloudfoundry/cf-release/commit/929aae4a2b6c6de20d48341c18bbe20b33bc432d>. If you're indeed deploying CF final version 212, the release notes for that version<https://github.com/cloudfoundry/cf-release/releases/tag/v212> recommend you deploy Diego final version 0.1304.0 alongside it. As long as you generate your deployment manifests from the commits for those final releases, it should have the consul service data in the correct format for the consul agent job. Thanks, Eric, CF Runtime Diego PM On Mon, Jul 13, 2015 at 3:29 PM, Shetty, Daya <Daya.Shetty(a)bnymellon.com<mailto:Daya.Shetty(a)bnymellon.com>> wrote: I¹m getting errors while deploying the diego release.. BOSH version 1.3012.0 CF release 212. Bosh Diego release 0.1367 $ bosh deployment ~/deployments/bosh-lite/cf.yml Deployment set to `/Users/xbbly9r/deployments/bosh-lite/cf.yml' $ bosh -n deploy ŠŠŠ Done binding instance vms > postgres_z1/0 (00:00:00) Done binding instance vms > consul_z1/0 (00:00:00) Done binding instance vms > nats_z1/0 (00:00:00) Done binding instance vms > etcd_z1/0 (00:00:00) Done binding instance vms > ha_proxy_z1/0 (00:00:00) Done binding instance vms > uaa_z1/0 (00:00:00) Done binding instance vms > hm9000_z1/0 (00:00:00) Done binding instance vms > api_z1/0 (00:00:00) Done binding instance vms > router_z1/0 (00:00:00) Done binding instance vms > runner_z1/0 (00:00:00) Done binding instance vms > loggregator_trafficcontroller_z1/0 (00:00:00) Done binding instance vms > doppler_z1/0 (00:00:00) Done binding instance vms (00:00:00) Started preparing configuration > Binding configuration. Failed: Error filling in template `agent_ctl.sh.erb' for `uaa_z1/0' (line 31: undefined method `tr' for ["uaa", {}]:Array) (00:00:01) Error 100: Error filling in template `agent_ctl.sh.erb' for `uaa_z1/0' (line 31: undefined method `tr' for ["uaa", {}]:Array) $ bosh deployment ~/deployments/bosh-lite/diego.yml Deployment set to `/Users/xbbly9r/deployments/bosh-lite/diego.yml¹ Š. 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 preparing dns > Binding DNS. Done (00:00:00) Started preparing configuration > Binding configuration. Failed: Error filling in template `agent_ctl.sh.erb' for `database_z1/0' (line 31: undefined method `tr' for ["bbs", {}]:Array) (00:00:00) Error 100: Error filling in template `agent_ctl.sh.erb' for `database_z1/0' (line 31: undefined method `tr' for ["bbs", {}]:Array) Any ideas on what I can do to resolve these issues? Regards Daya PS: I have attached the debug logs for both the errors. The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org> https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org> https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org> https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. |
|
|
|
Gwenn Etourneau
Maybe silly question but did you run the "bin/add-route" script in the
bosh-lite directory ? On Fri, Jul 17, 2015 at 8:24 AM, Shetty, Daya <Daya.Shetty(a)bnymellon.com> wrote: Hi Eric, |
|
|
|
Shetty, Daya <Daya.Shetty@...>
Hi Gwen,
toggle quoted message
Show quoted text
I did run the add-route utility hence the 'route get' was succeeding as mentioned in my email below, but as I was working from home today, I disconnected from my office network and then re ran the add-route utility and to my surprise it does work now. The only difference I see between the previous route and now is that the interface now is correct (I.e. vboxnet1) and previously it was showing en0 which I think was incorrect. route get 10.244.0.34 route to: 10.244.0.34 destination: 10.244.0.0 mask: 255.255.224.0 gateway: 192.168.50.4 interface: vboxnet1 flags: <UP,GATEWAY,DONE,STATIC,PRCLONING> recvpipe sendpipe ssthresh rtt,msec rttvar hopcount mtu expire 0 0 0 0 0 0 1500 0 route get 10.244.0.34.xip.io<http://10.244.0.34.xip.io> route to: 10.244.0.34 destination: 10.244.0.34 gateway: 192.168.50.4 interface: en0 flags: <UP,GATEWAY,HOST,DONE,WASCLONED,IFSCOPE,IFREF> recvpipe sendpipe ssthresh rtt,msec rttvar hopcount mtu expire 0 0 0 0 0 0 1500 0 So will need to dig deeper on why it was 'en0' in the first place, but for now I think I can start deploying some test apps. :) Thanks Eric & Gwen for your help. Regards, Daya From: <cf-bosh-bounces(a)lists.cloudfoundry.org<mailto:cf-bosh-bounces(a)lists.cloudfoundry.org>> on behalf of Gwenn Etourneau <getourneau(a)pivotal.io<mailto:getourneau(a)pivotal.io>> Reply-To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Date: Thursday, July 16, 2015 at 6:05 PM To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Subject: Re: [cf-bosh] cloudfoundry-incubator / diego-release deploy failing Maybe silly question but did you run the "bin/add-route" script in the bosh-lite directory ? On Fri, Jul 17, 2015 at 8:24 AM, Shetty, Daya <Daya.Shetty(a)bnymellon.com<mailto:Daya.Shetty(a)bnymellon.com>> wrote:
Hi Eric, Agree, It has stumped me too, hence asking the list if anyone has seen this behavior. Logging into the bosh-lite VM I can run the cf commands fine but not from my MAC. Also tried curl & telnet to port 80 and both return errors so ruling out CF cli issue on Mac OS. curl http://api.10.244.0.34.xip.io/v2/info curl: (7) Couldn't connect to server $ telnet 10.244.0.34 80 Trying 10.244.0.34... telnet: connect to address 10.244.0.34<http://10.244.0.34>: Can't assign requested address telnet: Unable to connect to remote host Thanks Daya From: <cf-bosh-bounces(a)lists.cloudfoundry.org<mailto:cf-bosh-bounces(a)lists.cloudfoundry.org>> on behalf of Eric Malm <emalm(a)pivotal.io<mailto:emalm(a)pivotal.io>> Reply-To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Date: Thursday, July 16, 2015 at 8:57 AM To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Subject: Re: [cf-bosh] cloudfoundry-incubator / diego-release deploy failing Hi, Daya, Hmm, that sounds like something strange with the local networking on your machine. The 'can't assign requested address' error is coming from the Golang standard networking libraries, and may indicate that it's unable to allocate an ephemeral port for the connection to the target address. From your 'route' command output, it does look like you're correctly using the bosh-lite VM as your gateway. Are you able to run 'curl http://api.10.244.0.34.xip.io/v2/info' directly? Thanks, Eric On Wed, Jul 15, 2015 at 4:40 PM, Shetty, Daya <Daya.Shetty(a)bnymellon.com<mailto:Daya.Shetty(a)bnymellon.com>> wrote: Hi Eric, I have successfully deployed the Diego release as per the recommended compatible versions you mentioned, but now hitting the next road block while executing “cf api” commands. Also I have attached the deployed release details in a separate file. Any ideas what I can do to resolve this issue? Here are the details regarding the failure: diego-release $ cf api --skip-ssl-validation api.10.244.0.34.xip.io<http://api.10.244.0.34.xip.io> Setting api endpoint to api.10.244.0.34.xip.io<http://api.10.244.0.34.xip.io>... FAILED Error performing request: Get http://api.10.244.0.34.xip.io/v2/info: dial tcp 10.244.0.34:80<http://10.244.0.34:80>: can't assign requested address :diego-release $ route get 10.244.0.34.xip.io<http://10.244.0.34.xip.io> route to: 10.244.0.34 destination: 10.244.0.34 gateway: 192.168.50.4 interface: en0 flags: <UP,GATEWAY,HOST,DONE,WASCLONED,IFSCOPE,IFREF> recvpipe sendpipe ssthresh rtt,msec rttvar hopcount mtu expire 0 0 0 0 0 0 1500 0 :diego-release $ ping 192.168.50.4 PING 192.168.50.4 (192.168.50.4): 56 data bytes 64 bytes from 192.168.50.4<http://192.168.50.4>: icmp_seq=0 ttl=64 time=0.340 ms 64 bytes from 192.168.50.4<http://192.168.50.4>: icmp_seq=1 ttl=64 time=0.304 ms --- 192.168.50.4 ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.304/0.322/0.340/0.018 ms :diego-release $ Thanks in advance, Regards Daya From: <cf-bosh-bounces(a)lists.cloudfoundry.org<mailto:cf-bosh-bounces(a)lists.cloudfoundry.org>> on behalf of Eric Malm <emalm(a)pivotal.io<mailto:emalm(a)pivotal.io>> Reply-To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Date: Tuesday, July 14, 2015 at 7:01 PM To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Subject: Re: [cf-bosh] cloudfoundry-incubator / diego-release deploy failing Hi, Daya, Good luck with the refreshed deployment! Please do note that CF v213 was not recommended for general use, as it contained a CCDB migration that was not backwards compatible. For a new deployment, though, it may be fine. The recommended compatible version of Diego is 0.1353.0. The consul agent job in CF v213 uses the new consul service data format that allows tags to be specified for each registered service. If the jobs in your deployment manifests have consul.agent.services properties with entries of the form uaa: {}, the manifests should be configured correctly. If the entries have the form - uaa, it's the old format, which won't work for the newer version of the consul agent script template. Best, Eric On Tue, Jul 14, 2015 at 6:26 PM, Shetty, Daya <Daya.Shetty(a)bnymellon.com<mailto:Daya.Shetty(a)bnymellon.com>> wrote: Hi Eric, Thanks for responding, as far as I can tell, I did generate the deployment manifest correctly. But just to make sure I deleted the deployment and my cf-release repo and redid the whole process, currently uploading the cf-213.yml and will then deploy this version to see whether it syncs up the consul agent correctly. This time I’m following the steps mentioned in https://github.com/cloudfoundry/bosh-lite/blob/develop/docs/deploy-cf.md instead of the steps mentioned in https://github.com/cloudfoundry-incubator/diego-release. Will update you of any problems once I’m done deploying. Regards Daya From: <cf-bosh-bounces(a)lists.cloudfoundry.org<mailto:cf-bosh-bounces(a)lists.cloudfoundry.org>> on behalf of Eric Malm <emalm(a)pivotal.io<mailto:emalm(a)pivotal.io>> Reply-To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Date: Tuesday, July 14, 2015 at 3:39 PM To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Subject: Re: [cf-bosh] cloudfoundry-incubator / diego-release deploy failing Hi, Daya, It looks like the consul service data in your deployment manifests is incompatible with the data that the consul agent job expects to consume in its agent_ctl.sh.erb script template. These data structures did change after CF v212 was released, in this cf-release commit<https://github.com/cloudfoundry/cf-release/commit/929aae4a2b6c6de20d48341c18bbe20b33bc432d>. If you're indeed deploying CF final version 212, the release notes for that version<https://github.com/cloudfoundry/cf-release/releases/tag/v212> recommend you deploy Diego final version 0.1304.0 alongside it. As long as you generate your deployment manifests from the commits for those final releases, it should have the consul service data in the correct format for the consul agent job. Thanks, Eric, CF Runtime Diego PM On Mon, Jul 13, 2015 at 3:29 PM, Shetty, Daya <Daya.Shetty(a)bnymellon.com<mailto:Daya.Shetty(a)bnymellon.com>> wrote: I¹m getting errors while deploying the diego release.. BOSH version 1.3012.0 CF release 212. Bosh Diego release 0.1367 $ bosh deployment ~/deployments/bosh-lite/cf.yml Deployment set to `/Users/xbbly9r/deployments/bosh-lite/cf.yml' $ bosh -n deploy ŠŠŠ Done binding instance vms > postgres_z1/0 (00:00:00) Done binding instance vms > consul_z1/0 (00:00:00) Done binding instance vms > nats_z1/0 (00:00:00) Done binding instance vms > etcd_z1/0 (00:00:00) Done binding instance vms > ha_proxy_z1/0 (00:00:00) Done binding instance vms > uaa_z1/0 (00:00:00) Done binding instance vms > hm9000_z1/0 (00:00:00) Done binding instance vms > api_z1/0 (00:00:00) Done binding instance vms > router_z1/0 (00:00:00) Done binding instance vms > runner_z1/0 (00:00:00) Done binding instance vms > loggregator_trafficcontroller_z1/0 (00:00:00) Done binding instance vms > doppler_z1/0 (00:00:00) Done binding instance vms (00:00:00) Started preparing configuration > Binding configuration. Failed: Error filling in template `agent_ctl.sh.erb' for `uaa_z1/0' (line 31: undefined method `tr' for ["uaa", {}]:Array) (00:00:01) Error 100: Error filling in template `agent_ctl.sh.erb' for `uaa_z1/0' (line 31: undefined method `tr' for ["uaa", {}]:Array) $ bosh deployment ~/deployments/bosh-lite/diego.yml Deployment set to `/Users/xbbly9r/deployments/bosh-lite/diego.yml¹ Š. 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 preparing dns > Binding DNS. Done (00:00:00) Started preparing configuration > Binding configuration. Failed: Error filling in template `agent_ctl.sh.erb' for `database_z1/0' (line 31: undefined method `tr' for ["bbs", {}]:Array) (00:00:00) Error 100: Error filling in template `agent_ctl.sh.erb' for `database_z1/0' (line 31: undefined method `tr' for ["bbs", {}]:Array) Any ideas on what I can do to resolve these issues? Regards Daya PS: I have attached the debug logs for both the errors. The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org> https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org> https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org> https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org> https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. |
|
|