Certificate metadata missing from controller websocket model
Bug #1977895 reported by
Caleb Ellis
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Low
|
Jack Lloyd-Walters | ||
Bug Description
Machines and pods include a `certificate` key with extra metadata (CN, expiration etc) if the power parameters include `certificate` and `key` fields. This key should also be added to the controller details websocket model.
Related branches
~lloydwaltersj/maas:controller-certificate-metadata
- MAAS Lander: Approve
- Alexsander de Souza: Approve
-
Diff: 34 lines (+14/-1)1 file modifiedsrc/maasserver/websockets/handlers/controller.py (+14/-1)
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| Changed in maas: | |
| assignee: | nobody → Jack Lloyd-Walters (lloydwaltersj) |
| status: | Triaged → In Progress |
| Changed in maas: | |
| milestone: | none → 3.3.0 |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| milestone: | 3.3.0 → 3.3.0-beta1 |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
