[BUG]Salt state.apply pip.installed not found, but salt-call state.apply work
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 5.6k
- Avg merge
- 2d 44m
- Merged PRs (30d)
- 80
Description
Description
Trying updating pip
{{ sls }} update_pip:
pip.installed:
- name: pip
- upgrade: True
- reload_modules: true
Work with salt-call state.apply from the minion but not from salt 'srv' state.apply giving the errror :
State 'pip.installed' was not found in SLS 'odoo-bare'
Reason: 'pip.installed' is not available.
Setup
(Please provide relevant configs and/or SLS files (be sure to remove sensitive info. There is no general set-up of Salt.)
Debian 12.0 master
Ubuntu 22.04 minion
Please be as specific as possible and give set-up details.
- on-prem machine
- VM (Virtualbox, KVM, etc. please specify)
- VM running on a cloud service, please be explicit and add details
- [ X ] container (Kubernetes, Docker, containerd, etc. please specify)
- or a combination, please be explicit
- jails if it is FreeBSD
- classic packaging
- [ X ] 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 the issue with the stated Debian 12 master, Ubuntu 22.04 minion, container, and onedir setup. Compare salt-call state.apply on the minion with salt 'srv' state.apply using the shown pip.installed state; done when the remote state also resolves that state successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100