Incorrect usage reported in Horizon for downsized Vms

Bug #1670786 reported by Radoslav
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Expired
Undecided
Unassigned

Bug Description

When instance is downsized storage does not shrink. When one views quota usage in horizon it shows the current flavor disk size which is not correct. Actual disk size is the biggest flavor disk size the instance has been resized to.

Lucas H. Xu (xuh-2)
Changed in horizon:
status: New → Confirmed
Revision history for this message
Kyrylo Romanenko (kromanenko) wrote :

Hello, Radoslav. Do instance shrinking by itself works properly?

Revision history for this message
Radoslav (radoslav-milanov) wrote : Re: [Bug 1670786] Re: Incorrect usage reported in Horizon for downsized Vms

Depends what do you mean by "instance shrinking":

Memory and CPU gets decreased, storage does not - most images use xfs
which supports only growing so storage does not shrink. But horizon
thinks storage has shrunk for usage calculation and this allows for
users to cheat on storage quotas.

On 7.9.2017 г. 11:04 ч., Kyrylo Romanenko wrote:
> Hello, Radoslav. Do instance shrinking by itself works properly?
>

Revision history for this message
Kyrylo Romanenko (kromanenko) wrote :

Thanks!

Revision history for this message
Kyrylo Romanenko (kromanenko) wrote :

It seems that Horizon counts on Volumes and Volume Storage gauges only Cinder volumes, not regarding to Instances and their flavors.

Revision history for this message
Kyrylo Romanenko (kromanenko) wrote :

For example i have resized instance from 5 to 10 Gb and this did not changed readings on Volumes and Storage gauges.

Revision history for this message
Radoslav (radoslav-milanov) wrote :

I observed the issue with VM ephemeral storage.

Thanks.

On 8.9.2017 г. 09:11 ч., Kyrylo Romanenko wrote:
> For example i have resized instance from 5 to 10 Gb and this did not
> changed readings on Volumes and Storage gauges.
>
> ** Attachment added: "resize_up.png"
> https://bugs.launchpad.net/horizon/+bug/1670786/+attachment/4946539/+files/resize_up.png
>

Revision history for this message
Radoslav (radoslav-milanov) wrote :

It seems latest Ocata code does not allow the resize operation to
complete if target disk size is smaller than current one so this might
no longer be an issue.

On 8.9.2017 г. 09:11 ч., Kyrylo Romanenko wrote:
> For example i have resized instance from 5 to 10 Gb and this did not
> changed readings on Volumes and Storage gauges.
>
> ** Attachment added: "resize_up.png"
> https://bugs.launchpad.net/horizon/+bug/1670786/+attachment/4946539/+files/resize_up.png
>

Revision history for this message
Ying Zuo (yingzuo) wrote :

It's not very clear what the issue is for this ticket. What usage quota is incorrect and where do you see it?

Changed in horizon:
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for OpenStack Dashboard (Horizon) because there has been no activity for 60 days.]

Changed in horizon:
status: Incomplete → Expired
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.