Cannot update controller tags using websocket API

Bug #1968102 reported by Caleb Ellis
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Alberto Donato

Bug Description

This likely came about when switching to returning tag IDs instead of tag names. The controller update websocket method seems to ignore passing a list of IDs to update tags.

Request:
{
  "type": 0,
  "request_id": 999,
  "method": "controller.update",
  "params": {
    "system_id": "knpge8",
    "tags": [1]
  }
}

Response:
{
  "type": 1,
  "request_id": 999,
  "rtype": 0,
  "result": {
    "system_id": "knpge8",
    "tags": [67, 25],
    ...remaining controller data
  }
}

This seems to only be an issue for controllers - machines and devices work as intended.

Related branches

Huw Wilkins (huwshimi)
Changed in maas:
milestone: none → 3.2.0
importance: Undecided → High
Alberto Donato (ack)
Changed in maas:
status: New → Triaged
assignee: nobody → Alberto Donato (ack)
status: Triaged → In Progress
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
milestone: 3.2.0 → 3.2.0-beta2
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.