You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
but after installing, salt is unaware which version was installed:
----------ID: couchdbFunction: pkg.installedResult: FalseComment: The following packages failed to install/update: couchdb=1.6.1Started: 17:03:55.342000Duration: 82181.0 msChanges:
----------couchdb:
----------new:
Not Foundold:
I finally tracked down the issue and it is because the CouchDB installer doesn't set the DisplayVersion registry entry needed by salt. I have worked around this issue by using the windows registry state:
But using this workaround, a highstate always reports a failure the first time it is executed (then success every time afterwards). I attempted to set the registry entry before running the installer, but the installer overwrites the key during the installation process.
Looking for advice on on any better way to solve this issue.
The text was updated successfully, but these errors were encountered:
I believe this has been addressed with saltstack/salt#31420. Expect to see it in the next 2015.8 release which I believe is 2015.8.8. Basically, if it doesn't find a version number in the registry, it will try to find it in the software definition matching off the full name.
I have an sls that installs CouchDB:
but after installing, salt is unaware which version was installed:
I finally tracked down the issue and it is because the CouchDB installer doesn't set the
DisplayVersion
registry entry needed by salt. I have worked around this issue by using the windows registry state:But using this workaround, a highstate always reports a failure the first time it is executed (then success every time afterwards). I attempted to set the registry entry before running the installer, but the installer overwrites the key during the installation process.
Looking for advice on on any better way to solve this issue.
The text was updated successfully, but these errors were encountered: