maas commands occasionally fail with NO_CERTIFICATE_OR_CRL_FOUND when TLS is enabled
Bug #2012139 reported by
Chris Johnston
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Anton Troyanov | ||
3.2 |
Fix Released
|
High
|
Anton Troyanov | ||
3.3 |
Fix Committed
|
High
|
Anton Troyanov |
Bug Description
Discovered while using FCE to deploy MAAS, after enabling TLS I occasionally see maas commands fail with NO_CERTIFICATE_
A reproducer can be something like:
until ! maas root node-results read system_id=X name=fce_blockdevs; do sleep 0.1; done
Related branches
~troyanov/maas:backport-ca3a5d0-3.2
- Anton Troyanov: Approve
- MAAS Lander: Approve
-
Diff: 55 lines (+22/-8)2 files modifiedsrc/maascli/api.py (+11/-8)
src/maascli/tests/test_api.py (+11/-0)
~troyanov/maas:backport-ca3a5d0-3.3
- Anton Troyanov: Approve
- MAAS Lander: Approve
-
Diff: 55 lines (+22/-8)2 files modifiedsrc/maascli/api.py (+11/-8)
src/maascli/tests/test_api.py (+11/-0)
~troyanov/maas:fix-cli-cert-race
Merged
into
maas:master
- Alberto Donato: Approve
- MAAS Lander: Approve
-
Diff: 55 lines (+22/-8)2 files modifiedsrc/maascli/api.py (+11/-8)
src/maascli/tests/test_api.py (+11/-0)
Changed in maas: | |
status: | New → Triaged |
assignee: | nobody → Anton Troyanov (troyanov) |
Changed in maas: | |
milestone: | none → 3.3.x |
importance: | Undecided → High |
milestone: | 3.3.x → 3.4.0 |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
milestone: | 3.4.0 → 3.4.0-beta1 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
subscribing ~field-high as this is blocking a deployment.