-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] pip.installed show stacktrace when user does not exists on testing #65458
Comments
I'm not sure if the changes should be shown. Maybe, the result should even be False, because the user isn't found and it cannot check if the package should be installed. It would then return something like:
Which is I think more the way it should be? |
When I'm lookung further into it, I even think that it should alsof fail with the same error when not running in dry-run mode. Currently, If I'm applying a
|
(cherry picked from commit 15cef7d)
(cherry picked from commit 15cef7d)
(cherry picked from commit 15cef7d)
Description
When I'm creating a state with
pip.installed
, with an user given and will apply this state withtest=True
then there will be a stacktrace because it's trying to figure out which packages are installed under that user. However the user does not exists, so it will fail to check.Setup
Install Salt 3006.3 on local linux machine. Install pip with your preferred package manager.
Steps to Reproduce the behavior
Create this state:
pip.sls:
The user
fred
does not exists. I'm applying the state:Expected behavior
When applying the state and test=True, something like this should be shown:
Versions Report
salt --versions-report
Additional context
I have installed Salt from the github repository with pip, checked out on tag v3006.3.
The text was updated successfully, but these errors were encountered: