"Deployed in memory" doesn't appear in the machine listing until a page reload

Bug #2057912 reported by Björn Tillenius
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Triaged
High
Unassigned
3.5
Triaged
High
Unassigned
maas-ui
New
Undecided
Unassigned

Bug Description

This is with MAAS 3.5.0~rc1-16224-g.6722880ff.

If I deploy a machine to memory, using the UI, the machine eventually transitions to "Deployed". But there's no mention of it being deployed in memory.

I have to reload the machine listing in order for the "Deployed in memory" note to appear.

Further more. If I manually (ssh to machine and "sudo reboot") reboot a machine having the "Deployed in memory" note, after the machine is rebooted, the note
disappears from the machine in the machine listing. If I reload the listing,
the note comes back.

Changed in maas:
status: New → Triaged
importance: Undecided → High
milestone: none → 3.6.x
no longer affects: maas-ui/3.5
Revision history for this message
Björn Tillenius (bjornt) wrote :

After I reboot a machine that's deployed in memory, I can see this websocket notification as it reboots (and gets redeployed):

{
 "type": 2,
 "name": "machine",
 "action": "update",
 "data": {
  "id": 2,
  "system_id": "xmfscq",
  "hostname": "toucan",
  "description": "",
  "pool": {
   "id": 0,
   "name": "default"
  },
  "domain": {
   "id": 0,
   "name": "maas"
  },
  "owner": "bjorn",
  "parent": null,
  "error_description": "",
  "zone": {
   "id": 1,
   "name": "default"
  },
  "cpu_count": 4,
  "memory": 16,
  "power_state": "on",
  "locked": false,
  "permissions": [
   "edit",
   "delete"
  ],
  "fqdn": "toucan.maas",
  "actions": [
   "on",
   "off",
   "release",
   "test",
   "rescue-mode",
   "mark-broken",
   "lock",
   "tag",
   "untag",
   "clone",
   "set-zone",
   "set-pool",
   "delete"
  ],
  "link_type": "machine",
  "tags": [],
  "physical_disk_count": 1,
  "storage": 120,
  "testing_status": {
   "status": -1,
   "pending": -1,
   "running": -1,
   "passed": -1,
   "failed": -1
  },
  "architecture": "amd64/generic",
  "osystem": "ubuntu",
  "distro_series": "jammy",
  "status": "Deployed",
  "status_code": 6,
  "simple_status": "Deployed",
  "fabrics": [
   "fabric-2",
   "fabric-3"
  ],
  "spaces": [],
  "extra_macs": [
   "80:3f:5d:09:f9:7d"
  ],
  "status_message": "Performing PXE boot",
  "pxe_mac": "b8:ae:ed:76:24:2d",
  "vlan": {
   "id": 3,
   "name": "Default VLAN",
   "fabric_id": 2,
   "fabric_name": "fabric-2"
  },
  "power_type": "amt",
  "ip_addresses": [
   {
    "ip": "10.5.32.7",
    "is_boot": true
   }
  ],
  "pod": null,
  "cpu_test_status": {
   "status": -1,
   "pending": -1,
   "running": -1,
   "passed": -1,
   "failed": -1
  },
  "memory_test_status": {
   "status": -1,
   "pending": -1,
   "running": -1,
   "passed": -1,
   "failed": -1
  },
  "network_test_status": {
   "status": -1,
   "pending": -1,
   "running": -1,
   "passed": -1,
   "failed": -1
  },
  "storage_test_status": {
   "status": -1,
   "pending": -1,
   "running": -1,
   "passed": -1,
   "failed": -1
  }
 }
}

description: updated
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.