ams cannot update instance info after resizing

Bug #2012989 reported by Shunde Zhang
6
This bug affects 1 person
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-allocation-rate: 4
  memory: 4GB
  memory-allocation-rate: 2
  gpu-slots: 0
  gpu-encoder-slots: 0
  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://anbox-cloud.io/docs/howto/install/deploy-juju
[2] https://pastebin.ubuntu.com/p/3ZpBVZnDnb/

summary: - ams cannot update instance spec after resizing
+ ams cannot update instance info after resizing
description: updated
Simon Fels (morphis)
Changed in anbox-cloud:
importance: Undecided → Low
importance: Low → Medium
status: New → Triaged
milestone: none → 1.18.0
Simon Fels (morphis)
Changed in anbox-cloud:
status: Triaged → In Progress
assignee: nobody → Simon Fels (morphis)
Simon Fels (morphis)
Changed in anbox-cloud:
status: In Progress → Fix Committed
Simon Fels (morphis)
Changed in anbox-cloud:
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.