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

The Wazuh indexer for Debian systems keeps asking to overwrite configuration files in the upgrade #417

Closed
rauldpm opened this issue Sep 19, 2024 · 1 comment
Labels
level/task Task issue type/bug Bug issue

Comments

@rauldpm
Copy link
Member

rauldpm commented Sep 19, 2024

Describe the bug
The Wazuh indexer for Debian systems asks users if they want to keep configurations files that introduce new changes, based on the #380 issue, this should not happen

Related wazuh/wazuh-qa#5753

To Reproduce
Steps to reproduce the behavior:

  1. Deploy a 4.8.2 All-In-One deployment using the Wazuh installation assistant
  2. Upgrade the Wazuh indexer to 4.9.1, check upgrade output

Expected behavior
The Wazuh indexer package for Debian systems should not ask the user to keep or not the new version, the new version should be added as a "new" file and not overwrite the current configuration file

Plugins
Default ones

Host/Environment (please complete the following information):

  • OS: Debian
  • Version: 12

Additional context

Unpacking wazuh-indexer (4.9.1-0) over (4.8.2-1) ...
Setting up wazuh-indexer (4.9.1-0) ...
Installing new version of config file /etc/default/wazuh-indexer ...

Configuration file '/etc/init.d/wazuh-indexer'
 ==> Deleted (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** wazuh-indexer (Y/I/N/O/D/Z) [default=N] ? N

Configuration file '/etc/wazuh-indexer/jvm.options'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** jvm.options (Y/I/N/O/D/Z) [default=N] ? N
Installing new version of config file /etc/wazuh-indexer/log4j2.properties ...
Installing new version of config file /etc/wazuh-indexer/opensearch-performance-analyzer/opensearch_security.policy ...

Configuration file '/etc/wazuh-indexer/opensearch-security/internal_users.yml'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** internal_users.yml (Y/I/N/O/D/Z) [default=N] ? N
Installing new version of config file /etc/wazuh-indexer/opensearch-security/roles.yml ...
Installing new version of config file /etc/wazuh-indexer/opensearch-security/roles_mapping.yml ...
Running Wazuh Indexer Post-Installation Script
@rauldpm rauldpm added level/task Task issue type/bug Bug issue labels Sep 19, 2024
@rauldpm rauldpm changed the title The Wazuh indexer for Debian systems keeps asking to overwrite configuration files The Wazuh indexer for Debian systems keeps asking to overwrite configuration files in the upgrade Sep 19, 2024
@wazuhci wazuhci moved this to Triage in Release 4.9.1 Sep 20, 2024
@AlexRuiz7
Copy link
Member

That's the expected behavior: #410 (comment)

@AlexRuiz7 AlexRuiz7 closed this as not planned Won't fix, can't repro, duplicate, stale Sep 20, 2024
@wazuhci wazuhci moved this from Triage to Done in Release 4.9.1 Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level/task Task issue type/bug Bug issue
Projects
None yet
Development

No branches or pull requests

2 participants