Skip to content

Skip netty4 yaml test in FIPS mode #66842

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

Merged
merged 1 commit into from
Dec 29, 2020

Conversation

tvernum
Copy link
Contributor

@tvernum tvernum commented Dec 29, 2020

The "Netty loaded" YAML test asserts that the configured transport is
"netty4", however when in FIPS mode, the tests enable security and the
configured transport is "security4".

This change skips the netty4 yaml test when running in FIPS mode.

Resolves: #66818

The "Netty loaded" YAML test asserts that the configured transport is
"netty4", however when in FIPS mode, the tests enable security and the
configured transport is "security4".

This change skips the netty4 yaml test when running in FIPS mode.

Resolves: elastic#66818
@tvernum tvernum added >test Issues or PRs that are addressing/adding tests v8.0.0 v7.12.0 v7.11.1 :Security/FIPS Running ES in FIPS 140-2 mode labels Dec 29, 2020
@tvernum tvernum requested a review from BigPandaToo December 29, 2020 05:37
@elasticmachine elasticmachine added the Team:Security Meta label for security team label Dec 29, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-security (Team:Security)

@tvernum
Copy link
Contributor Author

tvernum commented Dec 29, 2020

The original plan was to add this to the yml test:

    - skip:
        reason: "transport is set to 'security4' in FIPS"
        features: fips_140

However, that means that the test suite ended up with no tests, which fails the build.
It is, however, OK to assumeFalse on all tests, which is why this has been resolved in the Java suite instead.

Copy link
Member

@jkakavas jkakavas left a comment

Choose a reason for hiding this comment

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

LGTM

@tvernum tvernum merged commit 22bc833 into elastic:master Dec 29, 2020
tvernum added a commit to tvernum/elasticsearch that referenced this pull request Dec 29, 2020
The "Netty loaded" YAML test asserts that the configured transport is
"netty4", however when in FIPS mode, the tests enable security and the
configured transport is "security4".

This change skips the netty4 yaml test when running in FIPS mode.

Resolves: elastic#66818
Backport of: elastic#66842
tvernum added a commit that referenced this pull request Dec 29, 2020
The "Netty loaded" YAML test asserts that the configured transport is
"netty4", however when in FIPS mode, the tests enable security and the
configured transport is "security4".

This change skips the netty4 yaml test when running in FIPS mode.

Resolves: #66818
Backport of: #66842
Copy link
Contributor

@BigPandaToo BigPandaToo left a comment

Choose a reason for hiding this comment

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

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Security/FIPS Running ES in FIPS 140-2 mode Team:Security Meta label for security team >test Issues or PRs that are addressing/adding tests v7.11.1 v7.12.0 v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Netty4ClientYamlTestSuiteIT.test {yaml=/10_basic/Netty loaded}" fails in fips mode
5 participants