Skip to content
This repository has been archived by the owner on Sep 21, 2022. It is now read-only.

v36.11.0
Compare
Choose a tag to compare
@pcf-core-services-writer pcf-core-services-writer released this 17 Feb 02:39
v36.11.0
8758e0c

v36.11.0

  • New feature: As a Space Developer, I'd like to be able to create read-only bindings to a Service Instance [#129885695], [#154575192]
  • Improved: The Operator would like pre-seeded users' passwords to be updated when changed in the manifest [#153529269]
  • Improved: Many small usability updates to download-logs, including now relying on bosh ssh rather than having manual SSH set up independently.
    • As an Operator, download-logs should leverage bosh CLI where possible so that I don't have to figure out ssh on each IaaS [#154609725]
    • As an Operator, I'd like to be able to distinguish the artifacts generated by download-logs [#154299373]
    • Bug fix: download_logs should not fail when a customer has other jobs installed that aren't readable by user vcap [#148156397]
    • As an Operator, it would be nice if download logs could contain the output of bosh vms and bosh instances [#154299563]
    • As a support team member, I'd like download-logs to include the sst log files [#154013852]

Dependency Updates and Bug Fixes

  • cf-mysql-release shall use MariaDB 10.1.30 [#154149018]

    • MariaDB 10.1.31 failed to build cleanly, we'll look into it and catch up in a coming release.

  • Bump cf-mysql-release to use xtrabackup 2.4.8 [#153101615]

  • Bug fix: Cluster nodes should not hang in pre-start after unclean shutdown of cluster [#153572034]

  • Bug fix: remove logging to syslog from cf-mysql-release [#153301323]

    We discovered that in switching over to syslog-release, we hadn't fully stopped independently sending logs to syslog. We've pared that back.

    • A known issue remains with routing-release, which may be addressed some time in the future. Track issue #97 for any updates.

Deprecation Notice: ARP Cache

When a MySQL server VM disappears, BOSH will recreate that VM with the same IP address. When that new VM does not share the same ethernet MAC address as the old one, switchboard will not be able to direct connections to the new VM.

BOSH has a feature to clear the old ethernet address from switchboard's cache, but this feature used to default to off. For this reason, switchboard contained a duplicate feature to ensure that it is able to reach the new VM.

Recently, we discovered that this code does not work when BOSH DNS is enabled. This bug has been fixed, see below. However, in doing, we've learned that the switchboard feature does not work on GCP, and possibly other IaaSes.

The BOSH feature is designed to work on any IaaS that BOSH supports. In a coming release, we will drop the duplicate switchboard feature.

We strongly suggest that you run all of your Directors with flush-arp enabled. If you do not have flush-arp enabled, you may encounter issues where switchboard is not able to reach a back end node, even after successful resurrection.

  • Bug fix: ARP Cache flushing broken in switchboard when BOSH DNS is enabled [does not fix GCP] [#154302130]

Changes to Manifest

  • No changes
Assets 2
Loading