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.
(cherry picked from commit ab109db73f)
Co-authored-by: Jonathan Budzenski <jon@elastic.co>
With the merge of #98213, pid and log file settings were moved from
command line options to kibana.yml. Package tests use a non-default
kibana.yml and these settings were not applied. This updates our
configuration to include these settings.
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>
