Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

3.5 - No feedback from UI when trying to download diagnostic file #4

Open
DimSumDev opened this issue May 16, 2024 · 0 comments
Open

Comments

@DimSumDev
Copy link
Owner

DimSumDev commented May 16, 2024

After creating a diagnostic file and starting the download, there is no feedback in the UI, i.e. no Window is popping up for selecting a download location. However, in the browser console, you can see that the download is already going on. But then, when in reaches 1 GB file size, it fails.

Steps to reproduce

  1. Open the browser console.
  2. Create a diagnostic job that covers a large time period so the file size will be greater than 1 GB. In our scenario, components WKC and CCS were selected with 30 min time period.
  3. Wait for the job to complete, then select to download the diagnostic file.
  4. There won't be any feedback in the UI.
  5. Follow the activity in the browser console.
  6. You see that the file is actually being processed but it fails when 1 GB file size is reached.

Workaround

The generated diagnostic file is located under user-home/serviceability/collectedLogs. The filename matches the ID associated with the diagnostics collection. To download it to your local node from user-home you can use the following command. Replace by the name of the OpenShift namespace in which CP4D was installed.

oc cp <namespace>/<nginx_pod>:/user-home/serviceability/<job_id>.zip <destination>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant