v0.4.0 testing tracker

See original GitHub issue

Checklist:

Validate successful qhub deploy and qhub destroy for each provider:

AWS
- password
- github
- auth0
Validate the following services:
- Log into keycloak as root user and add user
- Add user from command line
- Launch JupyterLab session with new user
- Launch dask-cluster and test auto-scaler
- Launch dask-gateway dashboard
- Validate conda-store environments are created and available
- Launch basic CDS Dashboard
- Launch Grafana (validate SSO)
- Qhub destroy (#1110)
Azure
- password
- github
- auth0
Validate the following services:
- Log into keycloak as root user and add user
- Add user from command line
- Launch JupyterLab session with new user
- Launch dask-cluster and test auto-scaler
- Launch dask-gateway dashboard
- Validate conda-store environments are created and available
- Launch basic CDS Dashboard
- Launch Grafana (validate SSO)
- Qhub destroy
DO
- password
- github
- auth0
Validate the following services:
- Log into keycloak as root user and add user
- Add user from command line
- Launch JupyterLab session with new user
- Launch dask-cluster and test auto-scaler
- Launch dask-gateway dashboard
- Validate conda-store environments are created and available
- Launch basic CDS Dashboard
- Launch Grafana (validate SSO)
- Qhub destroy
GGP
- password
- github
- auth0
Validate the following services:
- Log into keycloak as root user and add user
- Add user from command line
- Launch JupyterLab session with new user
- Launch dask-cluster and test auto-scaler
- Launch dask-gateway dashboard
- Validate conda-store environments are created and available
- Launch basic CDS Dashboard
- Launch Grafana (validate SSO)
- Qhub destroy
local/existing kubernetes cluster/minikube
- password
- github
- auth0
Validate the following services:
- Log into keycloak as root user and add user
- Add user from command line
- Launch JupyterLab session with new user
- Launch dask-cluster and test auto-scaler
- Launch dask-gateway dashboard
- Validate conda-store environments are created and available
- Launch basic CDS Dashboard
- Launch Grafana (validate SSO)
- Qhub destroy

Validate qhub upgrade is successful for each provider:

AWS
- Upgrade from v0.3.12/v0.3.13/v0.3.14 to v0.4.0
Azure
- Upgrade from v0.3.12/v0.3.13/v0.3.14 to v0.4.0
DO
- Upgrade from v0.3.12/v0.3.13/v0.3.14 to v0.4.0
GCP
- Upgrade from v0.3.12/v0.3.13/v0.3.14 to v0.4.0
local/existing kubernetes deployment/minikube
- Upgrade from v0.3.12/v0.3.13/v0.3.14 to v0.4.0

Validate qhub-ops.yaml workflow

github-actions
gitlab-ci

(outdated)

#1003 Testing

Minikube deployment
AWS
Azure
Digital Ocean
GCP

Keycloak

Use keycloak for user authentication, test:
- AWS
  - password
  - github
  - auth0
- Azure
  - password
  - github
  - auth0
- Digital Ocean
  - password
  - github
  - auth0
- GCP
  - password
  - github
  - auth0

Azure deployments fail see #978 for more details.

`qhub upgrade`

AWS

upgrade from qhub v0.3.12 to main - password auth
upgrade from qhub v0.3.12 to main - auth0 auth

DO

upgrade from qhub v0.3.12 to main - password auth
upgrade from qhub v0.3.12 to main - auth0 auth

Issue Analytics

State:
Created 2 years ago
Comments:16 (16 by maintainers)

Top GitHub Comments

1reaction

iameskildcommented, Feb 22, 2022

CICD workflows have been tested and a PR for the relevant bug fixes/modifications has been opened: #1086

1reaction

viniciusdccommented, Feb 4, 2022

@iameskild just to keep in mind during tests

The grafana dashboard needs a valid email address to be defined in the user config #1016
The dask gateway dashboards are indeed working, but due to trafik auto-generated cert not being trusted, the tls access to the dashboard link returns 404, using an accepted cert fixes it, can be include following this

Top Results From Across the Web

NCS v0.4.0 asset tracker application - "Faulting instruction address ...

When running the asset tracker application from the NCS repo tagged v0.4.0 the LTE Link Monitor gives the following output: AT+CFUN?

Contributing — pyribs (v0.4.0)

Fix Bugs: Look through the Issue Tracker for bugs. Anything tagged with “bug” and “help wanted” is open to whoever wants to implement...

Cerbos v0.4.0 :: Cerbos // Documentation

Testing support in the Go SDK. The Go client library now supports starting a Cerbos server in code to test your integration. You...

COVID-19 Testing Tracker | Department of Health

Test results data comes from the Electronic Clinical Laboratory Reporting System (ECLRS), a NYSDOH database that contains reported results from all the labs ......

refs/tags/gopls/v0.4.0 - tools - Git at Google

Others, including the Go guru and the test coverage tool, can be fetched with go get . Packages include a type-checker for Go...