Add readiness checks for Feast services in end to end test

[davidheryanto]

Feast and Kafka services started in test-end-to-end.sh are not checked for readiness. Errors are only discovered during pytest runs.

This pull request add the readiness checks for those services, so failure to start any of those services will immediately fail end to end test.

By failing early, it's easier to inspect the root cause of failing end to end tests.

Related to #330

[woop]

/lgtm

[davidheryanto]

/hold
Doing a bit more testing

[woop]

/lgtm

[woop]

Is this failing because of something else?

[davidheryanto]

/hold
Still failing due to this error

org.springframework.beans.BeanInstantiationException: Failed to instantiate [feast.core.model.Source]: Factory method 'getDefaultSource' threw exception; nested exception is java.lang.RuntimeException: org.apache.kafka.common.errors.TimeoutException: Aborted due to timeout.

[woop]

/retest

[davidheryanto]

/hold cancel

[woop]

/lgtm
/approve

[feast-ci-bot]

@davidheryanto: The following test failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
test-end-to-end	bb2ccdb	link	/test test-end-to-end

Full PR test history

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[feast-ci-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: davidheryanto, woop

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [davidheryanto,woop]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[feast-ci-bot]

@davidheryanto: Updated the config configmap in namespace default at cluster default using the following files:

• key config.yaml using file .prow/config.yaml

In response to this:

Feast and Kafka services started in test-end-to-end.sh are not checked for readiness. Errors are only discovered during pytest runs.

This pull request add the readiness checks for those services, so failure to start any of those services will immediately fail end to end test.

By failing early, it's easier to inspect the root cause of failing end to end tests.

Related to #330

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.