-
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
Allow packages on Windows client to be newer than latest in win_repo #11602
Comments
Thanks for opening this issue. I've assigned it to myself. I think this totally makes sense. |
Hm. This isn't a Windows specific issue. I think all OSes will exhibit this same behavior. @terminalmage what do you think the proper behavior should be in this type of situation? |
No, this isn't something that is a problem for other platforms. @eliasp I'm guessing you're pinning the version number in your SLS file? It'd be helpful if you posted the actual SLS you're using, as well as the version of Salt you are running. This is actually pretty basic troubleshooting information, without which it can be difficult to narrow down the issue. |
Sorry for leaving out some details. microsoft.securityessentials:
pkg:
- installed Master is on 2014.0 The win_repo definition for microsoft.securityessentials:
4.4.304.0:
installer: http://mse.dlservice.microsoft.com/download/A/3/8/A38FFBF2-1122-48B4-AF60-E44F6DC28BD8/enus/amd64/mseinstall.exe
full_name: Microsoft Security Essentials
reboot: False
install_flags: ' /s /runwgacheck'
msiexec: False
uninstaller: '%PROGRAMFILES%/Microsoft Security Client/Setup.exe'
uninstall_flags: ' /s /u' |
Fixed in #12670 |
I was wrong - re-opening + working on a fix. |
In some cases, it is required to let packages update themselves: - Some Windows updates increase the version number of installed packages while this version cannot be deployed standalone through a regular win_repo package - Allow users to apply timely critical updates on their own so they don't have to wait for the admins to provide the newest version (e.g auto updates of software such as Mozilla Firefox which allows to install updates through regular users without administrative permissions) Fixes saltstack#11602
When a Windows client updates its packages to a newer version than the latest version available in the win_repo, applying the state will not succeed for this client.
A way to allow clients to update packages by themselves is required, otherwise a situation like this will occur:
microsoft.securityessentials
in win_repo is4.4.304.0
.4.5.216.0
.The text was updated successfully, but these errors were encountered: