ams cannot update instance info after resizing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Anbox Cloud |
Fix Released
|
Medium
|
Simon Fels |
Bug Description
I deployed a multi-node Anbox cloud 1.17 with juju bundle [1].
In the initial deployment the LXD node was deployed using flavor 'medium' (2 core and 4GB ram).
Then I resized it to flavor 'large' (4 core and 8GB ram).
However in ams it is still showing 2 core and 4GB RAM.
$ amc node show lxd0
name: lxd0
managed: true
status: online
unscheduable: false
architecture: x86_64
disk:
pool: ams0
size: 20GB
network:
address: 10.5.0.245
bridge-mtu: 8958
config:
public-address: 10.5.0.245
cpus: 2
cpu-allocatio
memory: 4GB
memory-
gpu-slots: 0
gpu-encoder-
tags: []
gpus: {}
The instance has 4 cores and 8GB RAM as shown in [2].
Note that the instance has rebooted during resizing.
Maybe the code to automatically update instance info is not working properly.
[1] https:/
[2] https:/
summary: |
- ams cannot update instance spec after resizing + ams cannot update instance info after resizing |
description: | updated |
Changed in anbox-cloud: | |
importance: | Undecided → Low |
importance: | Low → Medium |
status: | New → Triaged |
milestone: | none → 1.18.0 |
Changed in anbox-cloud: | |
status: | Triaged → In Progress |
assignee: | nobody → Simon Fels (morphis) |
Changed in anbox-cloud: | |
status: | In Progress → Fix Committed |
Changed in anbox-cloud: | |
status: | Fix Committed → Fix Released |