Wrong information in task.info.result on cloning configuration error.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.3k
- Forks
- 763
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
If the spec.identity.hostname configuration fails in a cloning process, the task correctly stops with state error, but the task.info.result property is set to None, although a machine was copied and is in the vm list.
task.info.result should point to the misconfigured machine.
To reproduce you could take snobears snippet and set the hostname on the hostname prep line to something like "äöü" (or any non ascii-character for that matter)
Thanks in advance.
retooth
Contributor guide
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 linked snobears clone.py snippet, especially the hostname preparation line, and reproduce the non-ASCII hostname failure during cloning. Trace how the cloning error sets task.info.result; done means it points to the copied misconfigured machine instead of None.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100