## Summary
- Closes https://github.com/elastic/kibana-operations/issues/100
- Utilizes FIPS agent from elastic/ci-agent-images#686
- Adds dynamic agent selection during PR pipeline upload
- FIPS agents can be used with `FTR_ENABLE_FIPS_AGENT` env variable or
`ci:enable-fips-agent` label
- Removes agent image config from individual steps in favor of image
config for the whole pipeline.
- Steps can still override this config by adding `image`, `imageProject`
etc
- Adds a conditional assertion to `Check` CI step which validates that
FIPS is working properly
### Testing
- [Pipeline run using FIPS
agents](https://buildkite.com/elastic/kibana-pull-request/builds/215332)
- Failures are expected and this possibly ran with flaky tests
Closeselastic/kibana-operations#96
[new pipeline run](https://buildkite.com/elastic/kibana-fips/builds/28)
[old pipeline run](https://buildkite.com/elastic/kibana-fips/builds/24)
- Fixes OpenSSL compilation so that it does not overwrite the OS version
and break OS functionality.
- Fixes issue where ES would not start due to ML pipe being unable to
write to Vagrant synced folder.
- Reenabled ML in FIPS pipeline
- Fixes permission where Kibana could not write UUID file.
- Fixes smoke test exit code not reporting correctly.
- Fixes Buildkite annotation for failed tests
[example](https://buildkite.com/elastic/kibana-fips/builds/23).
- Switches the base VM image from RHEL9 to Ubuntu due to RHEL9
subscription requirements to install repo packages.
- This blocked installing Chrome, causing tests using Webdriver to fail.
---------
Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>
* Set NODE_ENV=production for bin/*
* add tests
* Revert "Set NODE_ENV=production for bin/*"
This reverts commit 8012ed6a2e.
* Revert "Revert "Set NODE_ENV=production for bin/*""
This reverts commit 2fd499c112.
* bump ansible logging verbosity
* upgrade base os
* update base images
* add specificity to docker image glob
* limit memory
* bump base vm memory
* more cpu
* decrease verbosity
* less downloads
* disable shared symlinks
* more logging
* bump concurrency to test stability
* add concurrency group
* revert
* parallelism
* Revert "parallelism"
This reverts commit 4cc00f7144.
There appears to be a brief moment after kibana starts where we are
listening for http connections but immediately closing requests to the
status API. The return code by ansible here is -1, so this adds that as
a valid response to retry.
With a recent virtualbox update, we're getting failures in CI with:
> The IP address configured for the host-only network is not within the
> allowed ranges. Please update the address used to be within the allowed
> ranges and run the command again.
This updates the IP range used to be compatible.
The socket timeout for testing whether the status page is available or
not is currently 30 seconds. This test was disabled for being flaky.
Reproducing this locally hasn't been straight forward, but I am seeing
an average of ~20 seconds, which is close enough to the timeout that I'd
like to rule out machine differences. This gives the status check 120
seconds before dropping the connection.
Related to #106749 and #107300
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
