maas commands occasionally fail with NO_CERTIFICATE_OR_CRL_FOUND when TLS is enabled

Bug #2012139 reported by Chris Johnston
10
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_OR_CRL_FOUND.

A reproducer can be something like:

until ! maas root node-results read system_id=X name=fce_blockdevs; do sleep 0.1; done

Tags: field-high

Related branches

Revision history for this message
Chris Johnston (cjohnston) wrote :

subscribing ~field-high as this is blocking a deployment.

tags: added: field-high
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
Alberto Donato (ack)
Changed in maas:
milestone: 3.4.0 → 3.4.0-beta1
Alberto Donato (ack)
Changed in maas:
status: Fix Committed → 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.