Bug 1808692
| Summary: | xtremio is reporting wrong free_capacity_gb | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Chen <cchen> | ||||||
| Component: | openstack-cinder | Assignee: | Rajat Dhasmana <rdhasman> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Tzach Shefi <tshefi> | ||||||
| Severity: | high | Docs Contact: | Chuck Copello <ccopello> | ||||||
| Priority: | urgent | ||||||||
| Version: | 10.0 (Newton) | CC: | eharney, gcharot, geguileo, jschluet, lmarsh, mvalsecc | ||||||
| Target Milestone: | async | Keywords: | OtherQA, Triaged, ZStream | ||||||
| Target Release: | 10.0 (Newton) | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| 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.
|
Story Points: | --- | ||||||
| Clone Of: | |||||||||
| : | 1811122 (view as bug list) | Environment: | |||||||
| Last Closed: | 2020-04-02 10:26:00 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | 1811122 | ||||||||
| Bug Blocks: | |||||||||
| Attachments: |
|
||||||||
Created attachment 1666590 [details]
scheduler.log
Created attachment 1666591 [details]
Detailed steps starting from line 843
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. 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 |
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: