Add check which audits for Allocations against resource providers which are invalid
Bug #1940719 reported by
Drew Freiberger
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
charm-openstack-service-checks |
Fix Released
|
Medium
|
Przemyslaw Lal |
Bug Description
Due to various failures of VM deployments and migrations, we sometimes have stale resource allocations against resource providers in the placement/nova_api database which cause "ghost" contention when scheduling resources.
This charm should audit all allocations against each resource provider and ensure that the allocations' instance is "not deleted or shelved" and "exists on the hypervisor matching the resource provider".
Related branches
~lihuiguo/charm-openstack-service-checks:bug/1940719
Merged
into
charm-openstack-service-checks:master
at
revision 0039949475878599d1faa650e5d8fdd9e8d864d0
- 🤖 prod-jenkaas-bootstack (community): Approve (continuous-integration)
- BootStack Reviewers: Pending requested
- BootStack Reviewers: Pending requested
-
Diff: 622 lines (+558/-1)6 files modifiedsrc/config.yaml (+10/-0)
src/files/plugins/check_allocations.py (+46/-0)
src/files/run_allocation_checks.py (+220/-0)
src/lib/lib_openstack_service_checks.py (+48/-0)
src/tests/unit/conftest.py (+3/-1)
src/tests/unit/test_check_allocations.py (+231/-0)
~przemeklal/charm-openstack-service-checks:add-allocations-check
Rejected
for merging
into
charm-openstack-service-checks:master
- Xav Paice (community): Approve
- 🤖 prod-jenkaas-bootstack (community): Approve (continuous-integration)
- Przemyslaw Lal: Abstain
- Giuseppe Petralia: Approve
- Alvaro Uria: Pending requested
- Dariusz Smigiel: Pending requested
- Zachary Zehring: Pending requested
- Joe Guo: Pending requested
- Linda Guo: Pending requested
- Andrea Ieri: Pending requested
- James Troup: Pending requested
- BootStack Reviewers: Pending requested
-
Diff: 646 lines (+563/-4)8 files modifiedsrc/config.yaml (+10/-0)
src/files/plugins/check_allocations.py (+46/-0)
src/files/run_allocation_checks.py (+220/-0)
src/layer.yaml (+3/-0)
src/lib/lib_openstack_service_checks.py (+48/-0)
src/tests/unit/conftest.py (+3/-1)
src/tests/unit/test_check_allocations.py (+231/-0)
src/wheelhouse.txt (+2/-3)
Changed in charm-openstack-service-checks: | |
status: | New → In Progress |
assignee: | nobody → Przemysław Lal (przemeklal) |
Changed in charm-openstack-service-checks: | |
importance: | Undecided → Medium |
milestone: | none → 22.01 |
Changed in charm-openstack-service-checks: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
One quick-win check for this could be ensuring allocation count for a given provider matches the number of vms/servers scheduled to the host:
$ os resource provider show $server1_ resource_ provider_ uuid --allocations --format yaml | grep resources | wc -l
37
$ os server list --all --host $server1_fqdn -fvalue | wc -l
28