Skip to content
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

[SALTSTACK] #621

Closed
moondog69 opened this issue Feb 15, 2024 · 3 comments
Closed

[SALTSTACK] #621

moondog69 opened this issue Feb 15, 2024 · 3 comments

Comments

@moondog69
Copy link

SALTSTACK is great but there is just one issue. When it doesn't work there is no documentation on what to do. I installed the latest Jammy and ran the installer all but 32 states installed correctly. This is the message I get

"WARN[0575] first failed state comment="One or more requisite failed: sift.python-packages.volatility.sift-python-volatility-community-plugins" component=installer run_num=282 sls=sift.python-packages.volatility"
INFO[0575] statistics component=installer failed=32 success=643 total=675
INFO[0575] salt-call completed but had failed states component=installer
FATA[0575] salt-call completed but had failed states
castsiftinstall.txt

@ekristen
Copy link
Contributor

Appreciate the feedback. We can definitely look to improve the documentation around this.

INFO[0670] log file location                             component=installer file=/var/cache/cast/installer/logs/saltstack.log
INFO[0670] results file location                         component=installer file=/var/cache/cast/installer/logs/results.yaml
WARN[0670] first failed state                            comment="One or more requisite failed: sift.scripts.vshot.sift-scripts-vshot" component=installer run_num=574 sls=sift.scripts.vshot
INFO[0670] statistics                                    component=installer failed=32 success=643 total=675
INFO[0670] salt-call completed but had failed states     component=installer

can you please provide the two log files referenced at the end.

@ekristen
Copy link
Contributor

@moondog69 if you can provide the above we can help troubleshoot.

@ekristen
Copy link
Contributor

There were some underlying issues with m2crypto that changed, this has been resolved in the latest v2024.02.24 version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants