cloudfoundry / cloudfoundry/stratos
Failed to create service instance with CF-ServiceInstanceOrganizationNotAuthorized issue
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
Stratos Version
4.4.0
Frontend Deployment type
- Cloud Foundry Application (cf push)
- Kubernetes, using a helm chart
- Docker, single container deploying all components
- npm run start
- Other (please specify below)
Backend (Jet Stream) Deployment type
- Cloud Foundry Application (cf push)
- Kubernetes, using a helm chart
- Docker, single container deploying all components
- Other (please specify below)
Expected behaviour
Create service instance successfully.
Actual behavior
Got the error 'Failed to create service instance: A service instance for the selected plan cannot be created in this organization. The plan is visible because another organization you belong to has access to it.. Code: CF-ServiceInstanceOrganizationNotAuthorized'
Steps to reproduce the behavior
Pre-step:
Create service broker and make sure Marketplace view has Services.
Steps:
- Select a Service
- Click '+' to create service instance
- Select an organization and space for the service instance,then next
- Select Plan, then next
- Skip Bind App (Optional) ,then next
- Input Service instance name and select Target for service parameters, then click 'Finish' button.
Log output covering before error and any error statements
Insert log hereCopy

Detailed Description
Context
Possible Implementation
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the service-instance creation flow in the Kubernetes Helm deployment, using the listed organization, space, plan, and target steps, and collect the missing log output around the CF-ServiceInstanceOrganizationNotAuthorized error. Trace the frontend request and its backend response to determine whether the UI selects an unauthorized organization or mishandles the platform error; done means an authorized plan creates successfully and the failure is reported correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, helm, kubernetes, typescript
- Domain
- cloud, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100