You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Open the browser console.
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.
Wait for the job to complete, then select to download the diagnostic file.
There won't be any feedback in the UI.
Follow the activity in the browser console.
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.
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
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.
The text was updated successfully, but these errors were encountered: