[2.4b3] Upgrading a rack controller doesn't automatically update image status or version
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Blake Rouse |
Bug Description
I had a MAAS cluster with 2region/racks and 1 rack controller, all running a dailybuild post b3 (pre-rc1).
I installed a new rack controller, but using MAAS 2.4b2 instead. Since there were connection issues with the rack controller, I then upgraded to the latest version (the same one as the rest), and noticed that:
1. rack controller would show its version to be b2 instead of the latest.
2. rack controller, although images showed as synced, it didn't show the date of last synced
Full rack-controller read: http://
grepping for versions:
ubuntu@maas00:~$ maas admin rack-controllers read | grep 2.4
# Region/rack
"version": "2.4.0~
# Region/rack
"version": "2.4.0~
# 1 rack
"version": "2.4.0~
# Another rack
"version": "2.4.0~
On rack restart, the rack correctly sends its version:
2018-05-09 09:00:14 provisioningser
2018-05-09 09:00:15 provisioningser
2018-05-09 09:00:15 provisioningser
2018-05-09 09:00:15 provisioningser
but it continues to show b2 in the DB.
Related branches
- Andres Rodriguez (community): Approve
- MAAS Lander: Pending (unittests) requested
-
Diff: 107 lines (+23/-19)4 files modifiedsrc/maasserver/rpc/rackcontrollers.py (+7/-12)
src/maasserver/rpc/tests/test_rackcontrollers.py (+6/-0)
src/provisioningserver/rpc/boot_images.py (+3/-4)
src/provisioningserver/rpc/tests/test_boot_images.py (+7/-3)
Changed in maas: | |
milestone: | none → 2.4.0rc1 |
importance: | Undecided → High |
status: | New → Triaged |
assignee: | nobody → Blake Rouse (blake-rouse) |
Changed in maas: | |
milestone: | 2.4.0rc1 → 2.4.0rc2 |
Changed in maas: | |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Anytime after: 2018-05-09 09:08:00