-
Notifications
You must be signed in to change notification settings - Fork 32
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
QA testing - Fix wrong condition in WXS #3139
Comments
Review data
Testing environment
Tested packages
Status
|
Windows 2012R2Reproduce the failure - Upgrade from 4.3.0 to 4.3.6 🔴 (error reproduced)
Clean installation of the new package 🟢
Upgrade from 3.x with the service stopped 🟢
Upgrade from 4.0.x with the service stopped 🟢
Upgrade from 4.3.x with the service stopped 🟢
Upgrade from 3.x with the service started 🟢
Upgrade from 4.0.x with the service started 🟢
Upgrade from 4.3.x with the service started 🟢
|
Windows XPReproduce the failure - Upgrade from 4.3.0 to 4.3.6 🔴 (error reproduced)
Clean installation of the new package 🟢
Upgrade from 3.x with the service stopped 🟢
Upgrade from 4.0.x with the service stopped 🟢
Upgrade from 4.3.x with the service stopped 🟢
Upgrade from 3.x with the service started 🟢
Upgrade from 4.0.x with the service started 🟢
Upgrade from 4.3.x with the service started 🟢
|
Windows Server 2016Reproduce the failure - Upgrade from 4.3.0 to 4.3.6 🔴 (error reproduced)
Clean installation of the new package 🟢
Upgrade from 3.x with the service stopped 🟢
Upgrade from 4.0.x with the service stopped 🟢
Upgrade from 4.3.x with the service stopped 🟢
Upgrade from 3.x with the service started 🟢
Upgrade from 4.0.x with the service started 🟢
Upgrade from 4.3.x with the service started 🟢
|
Windows Server 2022Reproduce the failure - Upgrade from 4.3.0 to 4.3.6 🔴 (error reproduced)
Clean installation of the new package 🟢
Upgrade from 3.x with the service stopped 🟢
Upgrade from 4.0.x with the service stopped 🟢
Upgrade from 4.3.x with the service stopped 🟢
Upgrade from 3.x with the service started 🟢
Upgrade from 4.0.x with the service started 🟢
Upgrade from 4.3.x with the service started 🟢
|
validate basic behavior of alertsClean installation of the new package 🟢
|
🟢 Everything seems to be working properly |
Description
We found an incorrect condition in the WXS file that caused the MSI installation to get stuck.
Proposed checks
Steps to reproduce
In a Windows machine with low resources (1 core and 500 MB of memory) install wazuh agent 4.3.0 and update to 4.3.6. The installation will take a long time in the
starting services
step and in the end it will probably return the following error:Expected results
Installation and upgrade work properly and the service remains running if it was running before the upgrade.
Configuration and considerations
The text was updated successfully, but these errors were encountered: