qa - test_rbac failing on assertion error

Bug #1879544 reported by Adam Stokes
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Charmed Kubernetes Testing
Fix Released
High
Unassigned

Bug Description

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

Test error:
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 284, in test_rbac
    await wait_for_process(model, "RBAC")
  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 60, in wait_for_process
    assert False
AssertionError: assert False

Revision history for this message
George Kraft (cynerva) wrote :

Failures occurs here: https://github.com/charmed-kubernetes/jenkins/blob/6fd5feefa8dc3bc3558cfce8c47f34bfa03861ac/jobs/integration/validation.py#L283-L284

The test configured kubernetes-master with authorization-mode=Node,RBAC, and then waited for the kube-apiserver process to come up with --authorization-mode=Node,RBAC.

However, according to crashdump, kubernetes-master is still configured with authorization-mode=AlwaysAllow.

Did the call to app.set_config not take effect? Could this be a libjuju bug?

George Kraft (cynerva)
Changed in charmed-kubernetes-testing:
importance: Undecided → Critical
status: New → Triaged
George Kraft (cynerva)
Changed in charmed-kubernetes-testing:
importance: Critical → High
Revision history for this message
Adam Stokes (adam-stokes) wrote :

I've got another test result showing the test_rbac failure with debug output from juju:

https://jenkaas.s3.amazonaws.com/d8f3d212-ff14-43f6-95bd-550db4816a75/index.html

Traceback (most recent call last):
  File "/var/lib/jenkins/slaves/jenkins-slave-4/workspace/validate-ck/arch/arm64/channel/edge/node/runner-validate/series/focal/snap_version/1.19/edge/jobs/integration/validation.py", line 285, in test_rbac
    await wait_for_process(model, "RBAC")
  File "/var/lib/jenkins/slaves/jenkins-slave-4/workspace/validate-ck/arch/arm64/channel/edge/node/runner-validate/series/focal/snap_version/1.19/edge/jobs/integration/validation.py", line 61, in wait_for_process
    assert False
AssertionError: assert False
 -------------------------------Captured log call--------------------------------
DEBUG juju.application:application.py:381 Setting config for kubernetes-master: {'authorization-mode': 'RBAC,Node'}
DEBUG juju.client.connection:connection.py:436 connection 4396254863712 -> {
  "type": "Application",
  "request": "Set",
  "version": 8,
  "params": {
    "application": "kubernetes-master",
    "options": {
      "authorization-mode": "RBAC,Node"
    }
  },
  "request-id": 88
}..snip

Revision history for this message
George Kraft (cynerva) wrote :

> Did the call to app.set_config not take effect? Could this be a libjuju bug?

Never mind. I think app.set_config is working fine. The crashdump shows authorization-mode=AlwaysAllow because test_rbac_flag ran afterward and reverted it.

Revision history for this message
Adam Stokes (adam-stokes) wrote :
Changed in charmed-kubernetes-testing:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.