Re: Release Notes for v210

Eric Malm <emalm@...>

Hi, all,

Please be aware that the Diego team has recently identified a goroutine and
memory leak in the Diego codebase for release 0.1247.0 that eventually
affects the performance of Diego's receptor component. Further
investigation has revealed that this leak was introduced in final release
0.1221.0 and fixed in 0.1259.0. Consequently, we do not recommend the use
of Diego final releases from 0.1221.0 through 0.1258.0 in long-running
environments. If you do need to mitigate this issue in such an environment,
issuing a 'monit restart' to each receptor process on the Diego 'access'
VMs once it consumes a majority of available memory on the VM should
suffice and should have negligible impact on the performance and
availability of the Diego backend, especially if more than one 'access' VM
is present in the Diego deployment.

The next final release of CF (namely, v211) will be accompanied by a Diego
final release that does not exhibit this problem. Additionally, the Diego
team has identified and corrected the gaps in our testing pipeline and
monitoring configuration that allowed this resource leak to slip through.

Thank you for your understanding, and please let me know if you have
further questions about this matter.

Eric, CF Runtime Diego PM

On Tue, May 26, 2015 at 10:59 PM, Dieu Cao <dcao(a)> wrote:

The cf-release v210 was released on May 23rd, 2015

- Addressed USN-2617-1 <>
- Removed fuse binaries from lucid64 rootfs . Apps running on
lucid64 stack requiring fuse should switch to cflinuxfs2 details
- fuse binaries updated on cflinuxfs2 rootfs. details
- [Experimental] Work continues on support for Asynchronous Service
Instance Operationsdetails
- Support for configurable max polling duration
- [Experimental] Work continues on /v3 and Application Process Types
details <>
- [Experimental] Work continues on Route API details
- [Experimental] Work continues on Context Path Routes details
- Work continues on support for Service Keys details
- Upgrade etcd server to 2.0.1 details
- Should be run as 1 node (for small deployments) or 3 nodes spread
across zones (for HA)
- Also upgrades hm9k dependencies. LAMB client to be upgraded in a
subsequent release. Older client is compatible.
- cloudfoundry/cf-release #670
<>: Be able to
specify timeouts for acceptance tests without defaults in the spec.
details <>
- Fix bug where ssl enabled routers were not draining properly details
- cloudfoundry/cloud_controller_ng #378
<>: current usage
against the org quota details


- Bumped to UAA 2.3.0 details

Used Configuration

- BOSH Version: 152
- Stemcell Version: 2889
- CC Api Version: 2.27.0

Commit summary
Compatible Diego Version

- final release 0.1247.0 commit

Manifest and Job Spec Changes

- properties.acceptance_tests.skip_regex added
- properties.app_ssh.host_key_fingerprint added
- properties.app_ssh.port defaults to 2222
- properties.uaa.newrelic added
- properties.login.logout.redirect.parameter.whitelist

On Sat, May 23, 2015 at 9:50 PM, James Bayer <jbayer(a)> wrote:

CVE-2015-3202 details:

CVE-2015-1834 details:

On Sat, May 23, 2015 at 9:41 PM, James Bayer <jbayer(a)> wrote:

please note that this release addresses CVE-2015-3202 and CVE-2015-1834
and we strongly recommend upgrading to this release. more details will be
forthcoming after the long united states holiday weekend.


Thank you,

James Bayer

Thank you,

James Bayer

cf-dev mailing list

cf-dev mailing list

Join to automatically receive all group messages.