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 |
|---|---|---|---|---|---|
| Login Issues with my.osc.edu | Outage |
Resolved |
Update: this is fixed. Original post: We are aware that some users may be experiencing issues logging into ... Read more |
1 year 11 months ago | 1 year 11 months ago |
| A reboot of the NetApp as part of an upgrade, starting from Monday, November 19, 2018 | Maintenance |
Resolved |
Updated on 12:49 PM Nov... Read more |
7 years 9 months ago | 7 years 9 months 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 2 months ago | 9 months 2 weeks ago |
| NAMD 2.11 precompiled binaries do not work | Software |
Resolved |
NAMD 2.11 precompiled binaries do not work. Please use NAMD 2.11 installed from the source and available via module namd/2.11. The NAMD 2.11 issue involves changes to the command charmrun... Read more |
10 years 7 months ago | 7 years 7 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 3 months ago | 8 months 4 weeks ago |
