orange-cloudfoundry/cf-ops-automation

bosh errands should trigger after each bosh deploy

poblin-orange opened this issue · 0 comments

Expected behavior

As a platform operator, i expect the bosh errand to be launched after each deploy

Observed behavior

errands is not launched:

  • if the manifest does not change (ie: change in xxx-versions.yml, deployment is triggered, but no manifest change as we use latest to let concourse override)

errands gives git error

  • if a rebase has been applied, and we try to launch manually the errand (as it was not triggered due to issue above)

Affected release

Reproduced on version x.y

Traces and logs