JupyterHub outage 2020-09-03
| Outage start | Thursday, September 03, 2020 10:11 a.m. |
| Expected end | Thursday, September 03, 2020 9:46 a.m. |
There was a brief outage of the JupyterHub environment this morning for 25 minutes, when a bad build was released.
Reported Outages
TACC Network maintenance 13 September 2020
| Outage start | Sunday, September 13, 2020 10 a.m. |
| Expected end | Sunday, September 13, 2020 12:50 p.m. |
As of 12:50 PM CDT, network service is restored.
Access to systems at TACC will be unavailable 13 September 2020 from 10:00 AM CDT to 4:00 PM CDT. This allows for upgrades to the TACC core network. Instances will continue to run, but there will be no access to services and systems hosted at TACC until the work is complete. This includes CHI@TACC, KVM@TACC, and the Chameleon portal. Please submit any questions via the Chameleon helpdesk.
CHI@UC planned network maintenance 2020-09-03
| Outage start | Thursday, September 03, 2020 9 a.m. |
| Expected end | Thursday, September 03, 2020 9:05 a.m. |
We will have a short maintenance window at CHI@UC this coming Thursday, September 3rd, from 9AM-10AM, to do some maintenance to our core networking equipment.
During this time, instance launches on CHI@UC may be unreliable. The Jupyter interface will still be operational, and connectivity to existing instances should not be affected.
Login outage 2020-07-27
| Outage start | Monday, July 27, 2020 12:10 p.m. |
| Expected end | Monday, July 27, 2020 2:25 p.m. |
In the early afternoon, a configuration change caused login failures on both the bare metal and KVM experimentation sites. When logging in, some users may have encountered errors during authentication. The error has since been isolated and patched.
Jupyter outage 2020-07-10
| Outage start | Friday, July 10, 2020 3:30 p.m. |
| Expected end | Friday, July 10, 2020 10:15 p.m. |
We are currently experiencing an outage of the shared Jupyter environment related to the remote storage of user directories. There is no indication of data loss but the system is unable to mount these remote volumes. You will not be able to access your Jupyter server until this is resolved.
TACC Network maintenance 19 July 2020
| Outage start | Sunday, July 19, 2020 10 a.m. |
| Expected end | Sunday, July 19, 2020 1:45 p.m. |
UPDATE:
As of Sunday, 19 Jul 2020 at 1:45 PM (CDT) network maintenance is complete and services should be available.
Access to systems at TACC will be unavailable 19 July 2020 from 10:00 AM CDT to 4:00 PM CDT. This allows for upgrades to the TACC core network. Instances will continue to run, but there will be no access to services and systems hosted at TACC until the work is complete. This includes CHI@TACC, KVM@TACC, and the Chameleon portal. Please submit any questions via the Chameleon helpdesk.
CHI@UC outage Jun 22
| Outage start | Sunday, June 21, 2020 8:37 a.m. |
| Expected end | Monday, June 22, 2020 12:11 p.m. |
We are experiencing an outage at UC that began at ~12am CST. It affects the CHI OpenStack cloud and the Jupyter notebook environment. We are working to restore service currently.
[CANCELLED] TACC Network maintenance 21 June 2020
| Outage start | Sunday, June 21, 2020 10 a.m. |
| Expected end | Sunday, June 21, 2020 2 p.m. |
UPDATE: Maintenance has been cancelled for now, and will be re-scheduled at a later date.
Certificate chain expiration
| Outage start | Monday, June 01, 2020 12 a.m. |
| Expected end | Tuesday, June 02, 2020 4 p.m. |
Due to a certificate expiration in the trust chain for the certificates providing SSL for Chameleon, some clients (e.g. Swift) could no longer verify the SSL termination for the endpoint. To correct this, a new chain was generated using https://whatsmychaincert.com and verified at that same site.
The outage is resolved.
TACC Network maintenance 10 May 2020
| Outage start | Sunday, May 10, 2020 10 a.m. |
| Expected end | Sunday, May 10, 2020 11:02 a.m. |
Update: The TACC network maintenance is now complete
Access to all TACC systems will be unavailable on 10 May 2020 from 10:00 AM CDT until 2:00 PM CDT. This is to allow for upgrades to the TACC core network hardware. Instances will continue to run, but users will have no access to CHI@TACC, KVM@TACC, and Chameleon portal until the upgrade is complete, including the Chameleon portal.