cloudfoundry / cloudfoundry/cloud_controller_ng
Routes with metadata cause error when deleting orphan routes
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 207
- Forks
- 373
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 56
Description
Issue
Calling the delete unmapped routes endpoint, either directly or through the CLI, causes an unknown error if the orphaned route has metadata.
Context
Found while implementing this endpoint for the Cloud Foundry Java Client. Problem doesn't appear directly when using the CLI as it has no facility (afaik) for making routes with metadata.
Steps to Reproduce
Create a minimal domain.
Create a route based on the domain with some metadata.
Hit the delete orphaned routes endpoint.
Expected result
Orphaned routes, if any, are deleted, and success is returned.
Current result
Delete fails with an UnknownError(10001): An unknown error occurred. message.
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 delete orphaned routes endpoint with an orphaned route that has metadata, then trace the route deletion handling and metadata path in the Cloud Controller. The issue is done when orphaned routes with metadata are deleted successfully through the endpoint and the CLI path no longer returns UnknownError(10001).
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100