Skip to content

External BOSH feature #39

@michaelmccaskill

Description

@michaelmccaskill

Maybe this is intentional but when using the External BOSH feature, I have to manually upload the releases from each forge in order to make service creation work. e.g.

$ cf cs postgresql standalone my-db
Creating service instance my-db in org infrastructure / shared-tools as admin...
OK

However, the creation later fails. Investigating my BOSH shows:

180  error  Thu Jan 14 19:04:29 UTC 2021  Thu Jan 14 19:04:30 UTC 2021  admin  postgresql-standalone-2dd1c068-5aa6-455c-b0c7-3f4246231450  create deployment  Job 'postgres' not found in release 'postgres' 

Having to manually investigate each forge and upload their releases seems wrong.

Metadata

Metadata

Assignees

No one assigned

    Labels

    PRIORITY: MediumUsable workaround, but should get fixed before next minor releaseTRIAGE: AcceptedTicket has been accepted for work to proceedTYPE: BugDefect in intended behaviour

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions