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

Vulnerability Detection E2E tests: Outdated configuration #5126

Closed
Tracked by #5183
Rebits opened this issue Mar 19, 2024 · 3 comments · Fixed by #5127
Closed
Tracked by #5183

Vulnerability Detection E2E tests: Outdated configuration #5126

Rebits opened this issue Mar 19, 2024 · 3 comments · Fixed by #5127
Assignees
Labels

Comments

@Rebits
Copy link
Member

Rebits commented Mar 19, 2024

Description

The latest update in version 4.8.0 - Beta 4 introduces significant modifications to the vulnerability detection module's configuration and behavior. As a result, these alterations have caused the E2E Vulnerability Detection test to fail consistently.

Investigation is imperative to identify and implement the necessary adjustments to the tests

@Rebits Rebits self-assigned this Mar 19, 2024
@wazuhci wazuhci moved this to In progress in Release 4.8.0 Mar 19, 2024
@Rebits Rebits changed the title Vulnerability Detection E2E tests: Outdated configuration and index name Vulnerability Detection E2E tests: Outdated configuration Mar 20, 2024
@Rebits
Copy link
Member Author

Rebits commented Mar 20, 2024

Currently, using the test's configuration produced the following errors in the environment:

2024/03/20 10:41:30 wazuh-modulesd: WARNING: (1230): Invalid element in the configuration: 'indexer.certificate'.
2024/03/20 10:41:30 wazuh-modulesd: WARNING: (1230): Invalid element in the configuration: 'indexer.key'.
	<indexer>
		<enabled>yes</enabled>
		<hosts>
			<host>https://INDEXER-IP:9200</host>
		</hosts>
			<ssl>
			<certificate_authorities>
				<ca>/etc/pki/filebeat/root-ca.pem</ca>
			</certificate_authorities>
		</ssl>
		<certificate>/etc/pki/filebeat/node-2.pem</certificate>
		<key>/etc/pki/filebeat/node-2-key.pem</key>
	</indexer>

@Rebits
Copy link
Member Author

Rebits commented Mar 20, 2024

Changed test configuration to:

	<indexer>
		<enabled>yes</enabled>     
		<hosts>
			<host>https://INDEXER-API:9200</host>  
		</hosts>
		<ssl>
			<certificate_authorities>
				<ca>/etc/pki/filebeat/root-ca.pem</ca>
			</certificate_authorities>
			<certificate>/etc/pki/filebeat/node-2.pem</certificate>
			<key>/etc/pki/filebeat/node-2-key.pem</key>
		</ssl>
	</indexer>

Now, indexer connector is working as expected

2024/03/20 11:05:55 indexer-connector: INFO: IndexerConnector initialized.
2024/03/20 11:05:56 wazuh-modulesd:content-updater: INFO: Starting scheduled action for 'vulnerability_feed_manager'
2024/03/20 11:05:56 wazuh-modulesd:content-updater: INFO: Action for 'vulnerability_feed_manager' started
2024/03/20 11:05:56 wazuh-modulesd:content-updater: INFO: Action for 'vulnerability_feed_manager' finished
2024/03/20 11:05:56 wazuh-modulesd:vulnerability-scanner: INFO: Vulnerability scanner module started


Updates the regex for waiting until the end of the vulnerability content process to:

INFO: Vulnerability scanner module started

@Rebits Rebits linked a pull request Mar 20, 2024 that will close this issue
@wazuhci wazuhci moved this from In progress to Pending review in Release 4.8.0 Mar 21, 2024
@wazuhci wazuhci moved this from Pending review to In review in Release 4.8.0 Mar 21, 2024
@rafabailon
Copy link
Member

LGTM

@wazuhci wazuhci moved this from In review to Pending final review in Release 4.8.0 Mar 21, 2024
@wazuhci wazuhci moved this from Pending final review to Done in Release 4.8.0 Mar 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants