stackhpc / stackhpc/ansible-collection-openstack
os_ratings doesn't update value hashmap service mappings
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 5
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
When you want to do code as infra with os_ratings on cloudkitty and update a price, as the hashmap service mappings exist, it's skipped. It doesn't check if the value in place is the correct value wanted.
stackhpc.openstack-0.2.4
ansible 2.16.12
TASK [stackhpc.openstack.os_ratings : List hashmap service mappings] ************************************************************************************************************************************************************************
ok: [ansible] => (item=volume.size)
TASK [stackhpc.openstack.os_ratings : Create hashmap service mappings] **********************************************************************************************************************************************************************
skipping: [ansible] => (item={'service': 'volume.size', 'cost': 1e-05, 'group': 'volume_XXX', 'type': 'flat'})
skipping: [ansible]
It's needed to delete it then it works
TASK [stackhpc.openstack.os_ratings : Create hashmap service mappings] **********************************************************************************************************************************************************************
changed: [ansible] => (item={'service': 'volume.size', 'cost': 1e-05, 'group': 'volume_XXXX', 'type': 'flat'})
It should be great to check if the value is correct and fix it if needed.
Thanks
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the os_ratings task named “Create hashmap service mappings” and the preceding “List hashmap service mappings” output. Trace how existing mappings are compared with each requested item, then verify that rerunning with a changed cost, group, or type updates the mapping without deleting it first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100