Known issue with an Unresolved Resolution state is an active problem under investigation; a temporary workaround may be available.
A known issue with a Resolved (workaround) Resolution state is an ongoing problem; a permanent workaround is available which may include using different software or hardware.
A known issue with Resolved Resolution state has been corrected.
| Title | Category |
Resolution |
Description | Posted | Updated |
|---|---|---|---|---|---|
| Unscheduled GPFS Outage | filesystem |
Resolved |
As of 11:30PM on June 16th, we have removed the GPFS filesystem from service due to a number of hardware failures. At this point, further hardware failures would put a large portion of the entire... Read more |
11 years 1 month ago | 11 years 1 month ago |
| Reached your pull rate limit while pull from Docker hub | Software |
Resolved (workaround) |
You might encounter an error when pulling from Docker hub: ERROR: toomanyrequests: Too Many Requests. or You have reached your...Read more |
5 years 1 month ago | 8 months 3 weeks ago |
| Group membership discrepancies | Account Management, client portal |
Resolved |
Group changes may not always propagate through to our HPC Systems, although they show in the Client Portal (my.osc.edu). Issue: if you are added to a project that is still in a REQUESTED... Read more |
7 years 1 month ago | 6 years 11 months ago |
| Python version mismatch in Jupyter + Spark instance | Software |
Resolved (workaround) |
You may encounter the following error message when running a Spark instance using a custom kernel in the Jupyter + Spark app: 25/04/25 10:49:01 WARN TaskSetManager:...Read more |
1 year 2 months ago | 8 months 3 days ago |
