Pivotal Platform v2.8 Breaking Changes

Page last updated:

This topic describes the breaking changes you need to be aware of when upgrading to Pivotal Platform v2.8. For more information about important preparation steps you must follow before beginning an upgrade, see Upgrading Pivotal Platform.

Pivotal Operations Manager

There are no breaking changes in this release of Ops Manager.

Pivotal Application Service (PAS)

See the following PAS breaking changes:

PAS v2.8.4 Stability Issues

WARNING: Pivotal advises that you do not upgrade to PAS v2.8.4 at this time. Pivotal is investigating issues reported with the stability of PAS v2.8.4.

If you have already upgraded to PAS v2.8.4 and are experiencing instability in your PAS deployment, such as cf push failure, contact Support.

CredHub Requires At Least One CredHub Instance

PAS v2.8 and later requires at least one CredHub instance. If the number of CredHub instances is set to 0, the deployment fails.

If you scaled the number of CredHub instances to 0 in PAS v2.7, check the number of CredHub instances in the Resource Config pane of the PAS v2.8 tile and increase to one or more instances before you apply changes for the upgrade.

For more information, see PAS Must Use At Least One CredHub VM in Pivotal Application Service v2.8 Release Notes.

Syslog Adapters Are Removed

Syslog Adapters are not supported in PAS v2.8. If you disabled Syslog Agents on PAS v2.7.7, you must enable Syslog Agents before you upgrade to v2.8.x. If you do not enable Syslog Agents prior to upgrade, the upgrade fails in order to prevent potential log loss.

To enable Syslog Agents on PAS v2.7.7, do one of the following:

  • Go to the System Logging pane in the PAS tile and select the Enable agent-based syslog egress for app logs checkbox.

  • Set the properties.syslog_agent_enabled property to true.

Pivotal Application Service for Windows (PASW)

There are no breaking changes in this release of PASW.

Pivotal Isolation Segment

See the following Pivotal Isolation Segment breaking changes:

Segment Name Property Is Renamed

The property .isolated_diego_cell.placement_tag is renamed .properties.compute_isolation and includes three new inputs. This may impact your platform automation scripts.

.properties.compute_isolation contains the following inputs:

  • .properties.compute_isolation.disabled to disable compute isolation

  • .properties.compute_isolation.enabled to enable compute isolation

  • .properties.compute_isolation.enabled.isolation_segment_name to add a placement tag for your Diego Cells when compute isolation is enabled

You must update any platform automation scripts that include .isolated_diego_cell.placement_tag to use the new .properties.compute_isolation name and inputs. You must either disable compute isolation or enable compute isolation and specify a placement tag with these inputs.

For more information, see Compute and Networking Isolation in Pivotal Isolation Segment v2.8 Release Notes.

For guidance on setting configuration values, see Compute and Networking Isolation in Installing Pivotal Isolation Segment.

Compute Isolation Must Be Enabled If Networking Isolation Is Enabled

In the Pivotal Isolation Segment v2.8 tile, you cannot disable compute isolation and enable networking isolation at the same time. In the Compute and Network Isolation pane, you can disable compute isolation by selecting Disable under Compute isolation. If you disable compute isolation, you must set Router sharding mode to No isolation segment. If Compute isolation is disabled and Router sharding mode is set to Isolation segment only, the apps in your isolation segment fail to schedule.

Compute isolation is enabled by default. However, isolation segments do not require compute isolation. For more information, see Compute and Networking Isolation in Pivotal Isolation Segment v2.8 Release Notes.

For more information about configuring or disabling compute and networking isolation, see Compute and Networking Isolation in Installing Pivotal Isolation Segment.