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

Tests are failing for the x-pack/packetbeat help enroll #195

Closed
v1v opened this issue Jun 15, 2021 · 1 comment
Closed

Tests are failing for the x-pack/packetbeat help enroll #195

v1v opened this issue Jun 15, 2021 · 1 comment
Labels

Comments

@v1v
Copy link
Member

v1v commented Jun 15, 2021

What

The test assertion for packetbeat help enroll doesn't contain 'Unknown help topic' is failing

This assertion was introduced a couple of years ago, see #105

Version

It uses the latest 8.0-SNAPSHOT version stored in gs://beats-ci-artifacts/snapshots/packetbeat

Log

[2021-06-15T08:54:22.828Z] TASK [test-beat : Get packetbeat help output for an X-Pack feature] ************
[2021-06-15T08:54:23.526Z] changed: [tester-awslinux]
[2021-06-15T08:54:23.526Z] changed: [tester-centos7-64]
[2021-06-15T08:54:23.526Z] changed: [tester-awslinux2]
[2021-06-15T08:54:23.526Z] changed: [tester-centos8-64]
[2021-06-15T08:54:23.526Z] 
[2021-06-15T08:54:23.526Z] TASK [test-beat : Check that packetbeat contains X-Pack features] **************
[2021-06-15T08:54:23.526Z] fatal: [tester-awslinux]: FAILED! => {
[2021-06-15T08:54:23.526Z]     "assertion": "'Unknown help topic' not in xpack_cmd_result.stderr", 
[2021-06-15T08:54:23.526Z]     "changed": false, 
[2021-06-15T08:54:23.526Z]     "evaluated_to": false, 
[2021-06-15T08:54:23.526Z]     "msg": "Assertion failed"
[2021-06-15T08:54:23.526Z] }
[2021-06-15T08:54:23.526Z] fatal: [tester-awslinux2]: FAILED! => {
[2021-06-15T08:54:23.526Z]     "assertion": "'Unknown help topic' not in xpack_cmd_result.stderr", 
[2021-06-15T08:54:23.526Z]     "changed": false, 
[2021-06-15T08:54:23.526Z]     "evaluated_to": false, 
[2021-06-15T08:54:23.526Z]     "msg": "Assertion failed"
[2021-06-15T08:54:23.526Z] }
[2021-06-15T08:54:23.526Z] fatal: [tester-centos7-64]: FAILED! => {
[2021-06-15T08:54:23.526Z]     "assertion": "'Unknown help topic' not in xpack_cmd_result.stderr", 
[2021-06-15T08:54:23.526Z]     "changed": false, 
[2021-06-15T08:54:23.526Z]     "evaluated_to": false, 
[2021-06-15T08:54:23.526Z]     "msg": "Assertion failed"
[2021-06-15T08:54:23.526Z] }
[2021-06-15T08:54:23.526Z] fatal: [tester-centos8-64]: FAILED! => {
[2021-06-15T08:54:23.526Z]     "assertion": "'Unknown help topic' not in xpack_cmd_result.stderr", 
[2021-06-15T08:54:23.526Z]     "changed": false, 
[2021-06-15T08:54:23.526Z]     "evaluated_to": false, 
[2021-06-15T08:54:23.526Z]     "msg": "Assertion failed"
[2021-06-15T08:54:23.526Z] }

You can see the whole log output in -> https://beats-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/Beats/pipelines/beats-tester-mbp/pipelines/PR-193/runs/1/nodes/93/steps/133/log/?start=0

How to reproduce it

$ GROUP=centos make run-group
@v1v v1v added the bug label Jun 15, 2021
@adriansr
Copy link
Contributor

This is caused by elastic/beats#25696, which removed the enroll subcommand.

We can revert #105, as I don't think the check makes sense now.

This was referenced Jun 15, 2021
@v1v v1v closed this as completed Jun 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants