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

Address test failures for SmokeTestWatcherWithSecurityIT #42092

Merged

Conversation

jakelandis
Copy link
Contributor

@jakelandis jakelandis commented May 10, 2019

There are likely multiple root causes to the seemingly random failures
generated by SmokeTestWatcherWithSecurityIT. This commit un-mutes this
this test, address one known cause and adds debug logging for this test.

The known root cause for one failure is that we can have a Watch running
that is reading data from an index. Before we stop Watcher we delete that
index. If Watcher happens to execute after deletion of the index but before
the stop of Watcher the test can fail. The fix here is to simply move the
index deletion after the stop of Watcher.

Related #35361
Related #30777
Related #33291
Related #29893

There are likely multiple root causes to the seemingly random failures
generated by SmokeTestWatcherWithSecurityIT. This commit un-mutes this
this test, address one known cause and adds debug logging for this test.

The known root cause for one failure is that we can have a Watch running
that is reading data from an index. Before we stop Watcher we delete that
index. If Watcher happens to execute after deletion of the index but before
the stop of Watcher the test can fail. The fix here is to simply move the
index deletion after the stop of Watcher.

Related elastic#35361
Related elastic#30777
Related elastic#35361
Related elastic#33291
Related elastic#29893
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features

Copy link
Contributor

@gwbrown gwbrown left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@jasontedor jasontedor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left a comment about the logging configuration.

# custom properties
#######################################

logger.watcher.name = org.elasticsearch.xpack.watcher
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's enough to say setting 'logger.org.elasticsearch.xpack.watcher', 'debug' etc. instead of adding an entire extra configuration file?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks @jasontedor , i wasn't aware that was possible. tested it and works great. fixed on 119322c

Copy link
Member

@jasontedor jasontedor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@jakelandis
Copy link
Contributor Author

@elasticmachine run elasticsearch-ci/1

1 similar comment
@jakelandis
Copy link
Contributor Author

@elasticmachine run elasticsearch-ci/1

@jakelandis jakelandis added v6.8.1 and removed v6.8.0 labels May 19, 2019
@jakelandis
Copy link
Contributor Author

ci didn't kick in again ... closing and re-opening to kick off CI

@jakelandis jakelandis merged commit 8bbd3e3 into elastic:master May 24, 2019
gurkankaymak pushed a commit to gurkankaymak/elasticsearch that referenced this pull request May 27, 2019
* Address test failures for SmokeTestWatcherWithSecurityIT

There are likely multiple root causes to the seemingly random failures
generated by SmokeTestWatcherWithSecurityIT. This commit un-mutes this
this test, address one known cause and adds debug logging for this test.

The known root cause for one failure is that we can have a Watch running
that is reading data from an index. Before we stop Watcher we delete that
index. If Watcher happens to execute after deletion of the index but before
the stop of Watcher the test can fail. The fix here is to simply move the
index deletion after the stop of Watcher.

Related elastic#35361
Related elastic#30777
Related elastic#33291
Related elastic#29893
@jakelandis jakelandis added v6.8.2 and removed v6.8.1 labels Jun 17, 2019
@jpountz jpountz added the >test Issues or PRs that are addressing/adding tests label Jul 5, 2019
@jpountz
Copy link
Contributor

jpountz commented Jul 5, 2019

@jakelandis Is there anything left to backport?

@jakelandis
Copy link
Contributor Author

@jpountz - I am trying to stabilize these tests in master before backporting. I will remove the backport versions and track this via the meta issue #42409

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/Watcher >test Issues or PRs that are addressing/adding tests v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants