dsabeti

WARNING: DATA RACE
Write at 0x00c420176370 by goroutine 32:
  code.cloudfoundry.org/bbs/controllers_test.glob..func1.6.1()
      /home/pivotal/workspace/diego-release/src/code.cloudfoundry.org/bbs/controllers/actual_lrp_lifecycle_controller_test.go:788 +0x1f3
  github.com/onsi/ginkgo/internal/leafnodes.(*runner).runSync()
      /home/pivotal/workspace/diego-release/src/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113 +0xbb
  github.com/onsi/ginkgo/internal/leafnodes.(*runner).run()
      /home/pivotal/workspace/diego-release/src/github.com/onsi/ginkgo/internal/leafnodes/runner.go:64 +0x17a
  github.com/onsi/ginkgo/internal/leafnodes.(*SetupNode).Run()
      /home/pivotal/workspace/diego-release/src/github.com/onsi/ginkgo/internal/leafnodes/setup_nodes.go:15 +0xa0

dsabeti

jobs:
- name: my-job
  plan:
    - task: my-task
      config:
        platform: linux
        image_resource:
          type: docker-image
          source:
            repository: busybox

dsabeti

capi-release 1.47.0 is marked as having downtime issues, so we rolled back to capi-release 1.46.0 in cf-deployment. Teams that have been using the release-candidate branch of cf-deployment may notice problems in their pipelines, caused by the fact that capi-release 1.47.0 included a database migration that got rolled back as well. Steps provided here should help teams resolve this issue.

To un-bork your environment based on release-candidate, you can take the following steps:

1. SSH to the API VM so that you can target the database node:

dsabeti

$ bosh -e cf-dsabeti releases
Using environment 'https://104.155.140.199:25555' as client 'admin'

Name                   Version   Commit Hash
binary-buildpack       1.0.11*   60f6b0e9+
capi                   1.24.0*   4a584508
cf-smoke-tests         18*       0f6a144
cflinuxfs2             1.113.0*  688f031b+
consul                 161*      d420d113

dsabeti

main