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

Package installation failures after VD refactor development #2763

Closed
3 tasks
MarcelKemp opened this issue Jan 11, 2024 · 1 comment
Closed
3 tasks

Package installation failures after VD refactor development #2763

MarcelKemp opened this issue Jan 11, 2024 · 1 comment
Labels
level/task Subtask issue request/operational Operational requests type/bug Bug issue

Comments

@MarcelKemp
Copy link
Member

Wazuh version Install type Action performed Platform
4.8.0 Manager Install deb/rpm

Description

Checks have failed on the next merge upward PR for a variety of reasons, although all seem to be related to the development of the VD refactor that has been merged to 4.8.0:

We need to check the root of the problem and fix it so that we can correctly generate and install the packages via GitHub actions, and so that the checks pass correctly.

Error details


    File not found: /build_wazuh/rpmbuild/BUILDROOT/wazuh-manager-4.8.1-merge.4.8.0.into.4.8.1.x86_64/var/ossec/queue/indexer/vd_states_template.json
    File not found: /build_wazuh/rpmbuild/BUILDROOT/wazuh-manager-4.8.1-merge.4.8.0.into.4.8.1.x86_64/var/ossec/vd_1.0.0_vd_4.8.0.tar.xz
    Directory not found: /build_wazuh/rpmbuild/BUILDROOT/wazuh-manager-4.8.1-merge.4.8.0.into.4.8.1.x86_64/var/ossec/queue/vd

DoD

  • Find the cause of the problems.
  • Fix the issues encountered.
  • Re-run the checks to verify that they are working correctly.
@MarcelKemp
Copy link
Member Author

The problem is in the target that GitHub action uses when running the tests, as they use the target of the version that the PR refers to.

To fix the problem, it is necessary to first merge the wazuh/wazuh repository and then run the wazuh-packages checks, that way they all pass correctly, as shown in the following PR:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level/task Subtask issue request/operational Operational requests type/bug Bug issue
Projects
None yet
Development

No branches or pull requests

2 participants