qa - test_dashboard fails on keyerror

[Adam Stokes]

Our test_dashboard is failing on 1.18/edge with the following traceback:

Traceback (most recent call last):
  File "/var/lib/jenkins/slaves/jenkins-slave-3/workspace/validate-ck/arch/amd64/channel/edge/node/runner-validate/series/bionic/snap_version/1.18/edge/jobs/integration/validation.py", line 343, in test_dashboard
    user = config["users"][0]["user"]["username"]
KeyError: 'username'

The full report: https://jenkaas.s3.amazonaws.com/41f14796-6d90-4c06-8a7b-f56094d80b57/index.html
The Crashdump: http://jenkaas.s3-website-us-east-1.amazonaws.com/41f14796-6d90-4c06-8a7b-f56094d80b57/artifacts.tar.gz

[George Kraft (cynerva)]

This is caused by the switch from basic auth to token auth. The kubeconfig won't have username and password anymore, it will just be token.

[John George (jog)]

It looks like a change was made to the test suite at commit 851d79ba948bd71b454f8d35829c4869c92614f1 to switch over to token. However, Solutions QA is running the validation suite against stable, so we are now seeing a KeyError on 'token'

=========================== short test summary info ============================
FAILED jobs/integration/validation.py::test_dashboard - KeyError: 'token'
========================= 1 failed, 1 warning in 1.13s =========================
ERROR: InvocationError: '/home/ubuntu/k8s-validation/.tox/py3/bin/pytest -v -s --junit-xml=/home/ubuntu/project/generated/kubernetes/k8s-suite/k8s-suite-junit.xml --controller=foundations-aws --model=kubernetes /home/ubuntu/k8s-validation/jobs/integration/validation.py::test_dashboard'

The bundle and test logs are available by following the link at the bottom of this test run:

https://solutions.qa.canonical.com/#/qa/testRun/f55bb927-6b9f-47a9-ae08-371bb24d850c

[Peter Jose De Sousa (pjds)]

Another issue which arises from this when using the OpenID provider is a keyerror on "token".

[Peter Jose De Sousa (pjds)]

Pastebin with the token issue: https://pastebin.canonical.com/p/V4FwybRh7v/

[Adam Stokes (adam-stokes)]

I believe as soon as we can get ck1 out with the updated charms your tests will be resolved

[Adam Stokes (adam-stokes)]

Fixed in https://github.com/charmed-kubernetes/jenkins/commit/0aedbe713801d317629a26cf16544aa9b3fe8e84