[fips140][configtls.TestTPM_loadCertificate] Skip test if GODEBUG=fips140=only is set
#14225
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When #13926 is merged, all unit tests in this repository will be run with
GODEBUG=fips140=onlyto help surface any FIPS-140 violations in all the Go modules in this repository.One such unit test that fails in these circumstances is
config/configtls.TestTPM_loadCertificate. However, the FIPS violation surfaced by this test is from the test code itself (as opposed to from OpenTelemetry Collector core code that the test is exercising), specifically when this call is made:opentelemetry-collector/config/configtls/tpm_test.go
Line 191 in 974da01
As such, this is not a FIPS violation we need to worry about when running the OpenTelemetry Collector. To prevent the unit test from failing when it's run with
GODEBUG=fips140=only, we skip it.Link to tracking issue
Fixes #13989
Testing
Run the
configtls.TestTPM_loadCertificateunit test withGODEBUG=fips140=only. Make sure OS is Linux and Go version is >= 1.24.6.