Bug 1808692 - xtremio is reporting wrong free_capacity_gb
Summary: xtremio is reporting wrong free_capacity_gb
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: async
: 10.0 (Newton)
Assignee: Rajat Dhasmana
QA Contact: Tzach Shefi
Chuck Copello
URL:
Whiteboard:
Depends On: 1811122
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-29 12:16 UTC by Chen
Modified: 2023-09-07 22:10 UTC (History)
6 users (show)

Fixed In Version: openstack-cinder-9.1.4-55.el7ost
Doc Type: Bug Fix
Doc Text:
In previous releases, the xtremio driver inaccurately reported the amount of available storage capacity. VMs using the Block Storage back end could fail to provision because the reported capacity was greater than the actual amount of available storage. With this release, the xtremio driver reports the correct amount of available storage capacity.
Clone Of:
: 1811122 (view as bug list)
Environment:
Last Closed: 2020-04-02 10:26:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
scheduler.log (10.29 MB, text/plain)
2020-02-29 12:45 UTC, Chen
no flags Details
Detailed steps starting from line 843 (199.26 KB, text/plain)
2020-02-29 12:48 UTC, Chen
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1773725 0 None None None 2020-03-02 12:24:39 UTC
OpenStack gerrit 570702 0 None MERGED [XtremIO] Remove provisioning factor when reporting 2020-07-07 05:26:30 UTC
Red Hat Issue Tracker OSP-28362 0 None None None 2023-09-07 22:10:01 UTC
Red Hat Product Errata RHBA-2020:1301 0 None None None 2020-04-02 10:26:07 UTC

Description Chen 2020-02-29 12:16:55 UTC
Description of problem:

xtremio is reporting wrong free_capacty_gb

Version-Release number of selected component (if applicable):

OSP10

How reproducible:

100%

Steps to Reproduce:
1.
2.
3.

Actual results:

The free_capacity_gb 518640.0 which is far larger than total_capacity_gb 26006. Seems the free_capacity_free is related to max_over_subscription_ratio

2020-02-25 19:38:13.473 701539 DEBUG cinder.scheduler.host_manager [req-1d9501d8-02a2-4aa9-aa6f-3b2323e2dd8d - - - - -] Received volume service update from hostgroup@XtremIO: {u'filter_function': None, u'goodness_function': u'100', u'thick_provisioning_support': False, u'provisioned_capacity_gb': 13283, u'multiattach': True, u'volume_backend_name': u'VMAX_FC_backend', u'thin_provisioning_support': True, u'free_capacity_gb': 518640.0, u'driver_version': u'1.0.8', u'total_capacity_gb': 26006, u'reserved_percentage': 0, u'QoS_support': False, u'max_over_subscription_ratio': 20.0, u'vendor_name': u'EMC', u'consistencygroup_support': True, u'storage_protocol': u'FC'} update_service_capabilities /usr/lib/python2.7/site-packages/cinder/scheduler/host_manager.py:450

Expected results:


Additional info:

Comment 2 Chen 2020-02-29 12:45:08 UTC
Created attachment 1666590 [details]
scheduler.log

Comment 3 Chen 2020-02-29 12:48:09 UTC
Created attachment 1666591 [details]
Detailed steps starting from line 843

Comment 7 Gregory Charot 2020-03-11 10:17:06 UTC
Bumping the priority to urgent so that it gets included in the next OSP10 Async.

This bug can potentially lead to workload outage since the storage backend reports more free space than what is actually available.

Comment 11 errata-xmlrpc 2020-04-02 10:26:00 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:1301


Note You need to log in before you can comment on or make changes to this bug.