MAAS Images show "last deployed" as null even after being deployed
Bug #2023207 reported by
Jack Lloyd-Walters
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Committed
|
Medium
|
Jack Lloyd-Walters | ||
| 3.4 |
Fix Released
|
Medium
|
Jack Lloyd-Walters | ||
Bug Description
The "last deployed" tab in the image listing should populate after an image has been deployed, as should the cli response to "boot-resources read". It seems this is not happening, despite tests passing that suggest it is.
Related branches
~r00ta/maas:lp-2027625-3.4
- MAAS Lander: Approve
- Jacopo Rota: Approve
-
Diff: 63 lines (+13/-14)2 files modifiedsrc/maasserver/models/bootresource.py (+11/-13)
src/maasserver/websockets/handlers/tests/test_bootresource.py (+2/-1)
~lloydwaltersj/maas:fix-last-delpoy-time
- MAAS Maintainers: Pending requested
-
Diff: 68 lines (+17/-15)3 files modifiedsrc/maasserver/models/bootresource.py (+6/-13)
src/maasserver/models/tests/test_node.py (+10/-0)
src/maasserver/websockets/handlers/bootresource.py (+1/-2)
~r00ta/maas:lp-2027625
- MAAS Lander: Approve
- Jack Lloyd-Walters: Approve
-
Diff: 63 lines (+13/-14)2 files modifiedsrc/maasserver/models/bootresource.py (+11/-13)
src/maasserver/websockets/handlers/tests/test_bootresource.py (+2/-1)
| Changed in maas: | |
| milestone: | none → 3.4.x |
| no longer affects: | maas/3.3 |
| Changed in maas: | |
| milestone: | 3.4.x → 3.5.0 |
| Changed in maas: | |
| status: | Triaged → Fix Committed |
To post a comment you must log in.
