cloudfoundry-community / cloudfoundry-community/cf-python-client
Issue with PCF Cloud Foundry Client's "Retrieve Recent Logs" Function Compatibility with TAS for VMs v4.0.3 (Cloudfoundry v1.35.1)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 55
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
Description
Description:
I am experiencing a compatibility issue with the PCF Cloud Foundry (PCF CF) client when trying to use the "Retrieve Recent Logs" function. The issue seems to arise specifically when working with TAS for VMs v4.0.3, where the underlying Cloudfoundry version used is 1.35.1.
Issue:
When attempting to retrieve recent logs using the PCF CF client with TAS for VMs v4.0.3, I encounter an error or unexpected behavior.
Error : raise InvalidStatusCode(HTTPStatus(response.status_code), body, response.headers.get("x-vcap-request-id"))
cloudfoundry_client.errors.InvalidStatusCode: NOT_FOUND = {"description": "The app could not be found: ", "error_code": "CF-AppNotFound", "code": 100004}
Steps to Reproduce:
Ensure that the application is running on the Pcf Platform: TAS for VMs v4.0.3.
Use the app.recent_logs() method from the cloudfoundry-client version 1.35.1 to retrieve logs for an App.
Observe the cloudfoundry_client.errors.InvalidStatusCode: NOT_FOUND error.
Environment
Pcf Platform: TAS for VMs v4.0.3
cloudfoundry-client version: 1.35.1
Contributor guide
No contributing guide indexed for this repository
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 at the app.recent_logs() entry point and reproduce the NOT_FOUND InvalidStatusCode against TAS for VMs v4.0.3 with Cloud Foundry 1.35.1. Trace the request and response handling for recent logs; done means the method retrieves logs successfully in the reported environment without the CF-AppNotFound error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100