[2.4b3] Upgrading a rack controller doesn't automatically update image status or version

Bug #1770126 reported by Andres Rodriguez
6
This bug affects 1 person
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://paste.ubuntu.com/p/VKxmbKBqfj/

grepping for versions:

ubuntu@maas00:~$ maas admin rack-controllers read | grep 2.4
        # Region/rack
        "version": "2.4.0~rc1-6946-g291c48e39-0ubuntu1~18.04.1",
        # Region/rack
        "version": "2.4.0~rc1-6935-g2abc01f10-0ubuntu1~18.04.1",
                "firmware_version": "0.2-4",
                "firmware_version": "0.2-4",
        # 1 rack
        "version": "2.4.0~rc1-6946-g291c48e39-0ubuntu1~18.04.1",
                "firmware_version": "0.2-4",
                "firmware_version": "0.2-4",
        # Another rack
        "version": "2.4.0~beta2-6865-gec43e47e6-0ubuntu1",
                "firmware_version": "0.2-4",

On rack restart, the rack correctly sends its version:

2018-05-09 09:00:14 provisioningserver.rpc.common: [debug] [RPC -> responding] AmpBox({b'system_id': b'ncyhd6', b'beacon_support': b'True', b'version': b'2.4.0~rc1-6946-g291c48e39-0ubuntu1~18.04.1', b'_answer': b'2'})
2018-05-09 09:00:15 provisioningserver.rpc.common: [debug] [RPC -> responding] AmpBox({b'system_id': b'ncyhd6', b'beacon_support': b'True', b'version': b'2.4.0~rc1-6946-g291c48e39-0ubuntu1~18.04.1', b'_answer': b'2'})
2018-05-09 09:00:15 provisioningserver.rpc.common: [debug] [RPC -> responding] AmpBox({b'system_id': b'ncyhd6', b'beacon_support': b'True', b'version': b'2.4.0~rc1-6946-g291c48e39-0ubuntu1~18.04.1', b'_answer': b'2'})
2018-05-09 09:00:15 provisioningserver.rpc.common: [debug] [RPC -> responding] AmpBox({b'system_id': b'ncyhd6', b'beacon_support': b'True', b'version': b'2.4.0~rc1-6946-g291c48e39-0ubuntu1~18.04.1', b'_answer': b'2'})

but it continues to show b2 in the DB.

Related branches

Changed in maas:
milestone: none → 2.4.0rc1
importance: Undecided → High
status: New → Triaged
assignee: nobody → Blake Rouse (blake-rouse)
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Anytime after: 2018-05-09 09:08:00

Revision history for this message
Andres Rodriguez (andreserl) wrote :
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
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.