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

Old Salt files can conflict with new make dev run #380

Closed
eloquence opened this issue Dec 17, 2019 · 2 comments
Closed

Old Salt files can conflict with new make dev run #380

eloquence opened this issue Dec 17, 2019 · 2 comments
Labels

Comments

@eloquence
Copy link
Member

On a Whonix 14 system, running make all failed with "Recursive requisite found", specifically reporting issues with the IDs anon-whonix, sys-whonix-template-config, whonix-ws-15-dvm, and qvm-appmenus --update whonix-ws-15-dvm. Full logs here:

https://gist.github.com/eloquence/38eaadfe38c17a590aa5912c74bc10b0

After poking around at issues with Whonix updates, I re-ran the relevant Salt state with sudo qubesctl state.sls qvm.anon-whonix. This produced the output logged here:

https://gist.github.com/eloquence/3b4332f935d076620949a6b2e40d4ca1

After this command, a make clean && make all run completed without error.

@emkll
Copy link
Contributor

emkll commented Dec 17, 2019

It seems like a salt file in your /srv/salt directory was conflicting with the latest changes introduced in master. Our make all target does not clean salt prior to running https://github.com/freedomofpress/securedrop-workstation/blob/master/Makefile#L10 . Perhaps calling clean-salt prior to prep-salt might resolve here.

We should also consider a sd-specific folder in /srv/salt/ to ensure reliability of salt cleanup.

@eloquence eloquence changed the title Provisioning fails w/ "Recursive requisite found" until sys-whonix salt state re-run Old Salt files can conflict with new make dev run Sep 12, 2020
@eloquence
Copy link
Member Author

The suggestion to run clean-salt prior to prep-salt is tracked in #434, so closing this specific report that is likely just a symptom of the issue.

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

No branches or pull requests

2 participants