stackhpc / stackhpc/ansible-role-libvirt-vm
Role shouldn't require libvirt_vm_memory_mb and libvirt_vm_vcpus to be set when destroying the VM
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 135
- Forks
- 73
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 1
Description
The libvirt_vm_vcpus and libvirt_vm_memory_mb variables are required by the stackhpc.libvirt-vm role even when setting libvirt_vm_state to absent. Using the role without them fails with the following error:
FAILED! => {"msg": "'libvirt_vm_vcpus' is undefined"}
See https://review.openstack.org/#/c/606132 for context.
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 by tracing where the role validates or uses libvirt_vm_vcpus and libvirt_vm_memory_mb when libvirt_vm_state is absent, using the failure message and the role entry point. Reproduce the reported invocation without those variables; done means destroying the VM no longer fails with an undefined-variable error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100