[Question] dask-staging helm release removal, intentional?

[GeorgianaElena]

Context

When going to the https://dask-staging.2i2c.cloud, itreturns a 404 and I don't see any pods in the dask-staging namespace

Proposal

No response

Updates and actions

• Redeploy the hub?

[GeorgianaElena]

Ok, hub is back up. Apparently the hem release was gone:

Release "dask-staging" does not exist. Installing it now.

I'll just keep this issue open for the day in case the deletion was intentional, otherwise I'll close the issue as resolved since probably this was by mistake.

[yuvipanda]

Apologies, this was on me! I was testing #1468, and the following happened:

-i was testing upgraidng to z2jh master on these staging hubs,

• When done, i deleted the helm releases of these staging hubs (as you can't 'downgrade' from z2jh master to 1.2)
  but, that didn't actually remove the test servers i had spun up! So they were still using home-nfs
• I ran the deployer locally, which succeeded - even though the home-nfs pvc was in 'Terminating'. helm doesn't consider this an error condition
• However, I didn't try to run the health check locally - so i thought things were back up (I checked if pods were running) but it wasn't

I must've forgotten to run it on dask-staging.