| Outage start | Tuesday, April 29, 2025 9 a.m. |
| Expected end | Tuesday, April 29, 2025 9 a.m. |
On April 29th, CHI@Edge will be inaccessible as we migrate the control-plane to more robust hosting and upgrade several dependent services. During the maintenance window, the dashboard, running containers, and device enrollement will be unavailable.
| Outage start | Thursday, April 10, 2025 9 a.m. |
| Expected end | Thursday, April 10, 2025 4:23 p.m. |
Resolved
To prepare for upgrades to KVM@TACC, we are scheduling maintenance starting at 9:00 AM CDT on Thursday April 10th.
During this time, Staff will Stop All Running Instances, perform upgrades, then restart those instances.
This work will ensure that VMs are compatible with following upgrades, preventing further downtime.
| Outage start | Monday, March 17, 2025 11:35 a.m. |
| Expected end | Monday, March 17, 2025 6 p.m. |
We're observing issues with leases for some devices in CHI@edge, and have identified some configuration inconistency on the backend that may be contributing. While debugging, there was a brief outage in the reservation api service, which manifested as a failure to load the "leases" dialog.
Thing seem to be back, but we're still investigating.
| Outage start | Tuesday, March 04, 2025 7:05 p.m. |
| Expected end | Wednesday, March 05, 2025 12 p.m. |
11AM March 5th:
This outage is now resolved, CHI@UC appears to be working as normal.
We don't yet have a root cause from our provider, but are working with them to prevent a repeat.
| Outage start | Monday, March 03, 2025 9 a.m. |
| Expected end | Tuesday, March 04, 2025 4:48 p.m. |
Resolved: Jupyter service should be working as normal.
Update: We are waiting on DNS updates to finish the updating of our Jupyter infrastructure, and so the outage is ongoing. Thank you for your patience.
We will be updating our Jupyter infrastructure on the morning of Monday, March 3, which will take down JupyterHub and running JupyterLab instances.
| Outage start | Tuesday, February 11, 2025 3 p.m. |
| Expected end | Tuesday, February 11, 2025 4:30 p.m. |
UPDATE: Jupyterhub service is back to normal
---
Users are experiencing errors when launching Jupyter environments on Chameleon's Jupyterhub. We are working on a resolution.
| Outage start | Wednesday, February 19, 2025 6 a.m. |
| Expected end | Wednesday, February 19, 2025 6:47 a.m. |
Resolved: Work has been completed.
TACC network infrastructure will not be available from 6:00AM to 7:00AM (CDT) on Wednesday, February 19 2025. Network maintenance will be performed during this time. This will impact access to the Chameleon Portal, JupyterHub, CHI@TACC, KVM@TACC, and CHI@Edge. Experiments and VMs will continue to run, but will not have connectivity outside of TACC.
| Outage start | Friday, February 07, 2025 10 a.m. |
| Expected end | Friday, February 07, 2025 1:26 p.m. |
Resolved: Instance launches on KVM@TACC are once again working.
Some users are experiencing the message "not enough hosts available" when attempting to launch an instance on KVM@TACC. Staff are troubleshooting the problem.
| Outage start | Wednesday, January 22, 2025 1 p.m. |
| Expected end | Wednesday, January 22, 2025 3:47 p.m. |
Resolved: Service has been restored for KVM@TACC
Starting at approximately 1:00 PM Central, KVM@TACC's authentication service has been interrupted. Staff is working to restore the service.
| Outage start | Tuesday, January 28, 2025 6 a.m. |
| Expected end | Tuesday, January 28, 2025 6 p.m. |
The Jan 28th maintenance window has concluded, and KVM@TACC is back to normal.
We were able to migrate the loadbalancer and database services to a redundant configuration, but had to roll back the migration of other control-plane services due to unforseen complications. We'll be investigating a path forward, and a subsequent (shorter) maintenance window to finish the migration for each service.