refresh a lxd KVM host resources after it was added
Bug #1973617 reported by
Laurent Sesquès
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Undecided
|
Unassigned | ||
maas-ui |
Fix Released
|
Unknown
|
Bug Description
Once a LXD KVM host has been added, its resources seem to be immutable - at least storage is.
Steps to reproduce:
1. Add a LXD host to MAAS
2. Change the storage resources for the LXD host (e.g. add more storage)
3. MAAS never refreshes the known capacities for the host, and for instance will refuse to add a virtual machine if it still thinks that it doesn't have enough storage
If no VMs were deployed to the host, deleting then re-adding the LXD host works around the issue.
This is using MAAS 3.1.0-10901-
tags: | added: ui |
Changed in maas-ui: | |
importance: | Undecided → Unknown |
status: | New → Fix Released |
Changed in maas: | |
status: | New → Fix Committed |
Changed in maas: | |
milestone: | none → 3.3.0 |
Changed in maas: | |
milestone: | 3.3.0 → 3.3.0-beta1 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
MAAS doesn't automatically refresh resources information for a VM host (except for updating used resources when machines get composed/removed from MAAS).
It's possible, though, to manually refresh the information, either from the UI (from the VM host dashboard) or the API (maas $profile vm-host refresh $id).
Doing so will refresh both VMs and cpu/storage/network information from the host.
Could you please try this and verify your changes are reflected?