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

FIX: Remove intca symlink on reinstall #12290

Merged

Conversation

petiepooo
Copy link
Contributor

The symlink is created in init.sls; it should be removed here.

The symlink is created in init.sls; it should be removed here.
@petiepooo
Copy link
Contributor Author

FYI, I'm working on having the ability to upgrade form ubuntu 20.04 with v2.3.280 to 22.04 with v2.4 without needing to reinstall the OS. This file was one of the issues causing the installation of v2.4.40 to fail. Under v2.3, it's a file, but v2.4 expects it to be a symlink.

@petiepooo
Copy link
Contributor Author

Also, when reinstall_init() is called, should the calls to the remove state at

logCmd "salt-call state.apply ca.remove -linfo --local --file-root=../salt"
be moved up to above where salt-master and salt-minion are stopped if that state is to be run successfully? Or does salt-call complete even if the salt-minion daemon is stopped?

salt-call does not work when the salt-master is not running.  If these calls are to succeed, they should occur before the salt services are stopped.
@petiepooo petiepooo changed the title also remove intca symlink fix: also remove intca symlink Feb 2, 2024
@TOoSmOotH TOoSmOotH changed the title fix: also remove intca symlink FIX: Remove intca symlink on reinstall Feb 12, 2024
@TOoSmOotH TOoSmOotH merged commit f91cb5b into Security-Onion-Solutions:2.4/dev Feb 12, 2024
2 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Feb 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants