[BUG] 3005 salt-cloud 'ascii' codec can't decode byte 0xe2
Open
Nobody has claimed this yet.
bug
Core
needs-triage
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 5.6k
- Avg merge
- 2d 44m
- Merged PRs (30d)
- 80
Description
Description
After upgrading to 3005 (onedir) salt-cloud reports ascii codec error.
[ERROR ] There was a query error: 'ascii' codec can't decode byte 0xe2 in position 80: ordinal not in range(128)
Setup
My template/map file
vmware:
server-name-001:
num_cpus: 1
memory: 2GB
dns_servers:
- 1.1.1.1
domain: example.tld
minion:
grains:
roles:
- highstate
folder: infrastructure
devices:
network:
Network adapter 1:
name: d1603_PROD
domain: example.tld
gateway: [10.0.0.1]
switch_type: distributed
subnet_mask: 255.255.0.0
- on-prem machine
- VM (Virtualbox, KVM, etc. please specify)
- VM running on a cloud service, please be explicit and add details: vmware
- container (Kubernetes, Docker, containerd, etc. please specify)
- or a combination, please be explicit
- jails if it is FreeBSD
- classic packaging
- onedir packaging
- used bootstrap to install
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 by reproducing salt-cloud with the supplied VMware map and the onedir/bootstrap setup, then trace where the reported ASCII decoding error is raised. The issue provides no file or test entry point; done means identifying and fixing the failure so this configuration no longer produces the reported codec error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100