NO-ISSUE: Extend waiting time to test DB container to be ready

[eliorerz]

Sometimes when debugging unittest without skipper the 5 seconds timeout is not enough and will fail if the test start before DB container is ready.
This PR extend the waiting to 30 seconds which is most of the time is enough.

List all the issues related to this PR

• New Feature
• Enhancement
• Bug fix
• Tests
• Documentation
• CI/CD

What environments does this code impact?

• Automation (CI, tools, etc)
• Cloud
• Operator Managed Deployments
• None

How was this code tested?

• assisted-test-infra environment
• dev-scripts environment
• Reviewer's test appreciated
• Waiting for CI to do a full test run
• Manual (Elaborate on how it was tested)
• No tests needed

/cc @osherdp @adriengentil

[openshift-ci-robot]

@eliorerz: This pull request explicitly references no jira issue.

In response to this:

Sometimes when debugging unittest without skipper the 5 seconds timeout is not enough and will fail if the test start before DB container is ready.
This PR extend the waiting to 30 seconds which is most of the time is enough.

List all the issues related to this PR

• New Feature
• Enhancement
• Bug fix
• Tests
• Documentation
• CI/CD

What environments does this code impact?

• Automation (CI, tools, etc)
• Cloud
• Operator Managed Deployments
• None

How was this code tested?

• assisted-test-infra environment
• dev-scripts environment
• Reviewer's test appreciated
• Waiting for CI to do a full test run
• Manual (Elaborate on how it was tested)
• No tests needed

/cc @osherdp @adriengentil

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.

[codecov]

Codecov Report

Merging #5425 (8888a5e) into master (83852f8) will decrease coverage by 0.05%.
Report is 23 commits behind head on master.
The diff coverage is 100.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5425      +/-   ##
==========================================
- Coverage   67.69%   67.64%   -0.05%     
==========================================
  Files         226      227       +1     
  Lines       33386    33427      +41     
==========================================
+ Hits        22600    22612      +12     
- Misses       8749     8779      +30     
+ Partials     2037     2036       -1     

Files Changed	Coverage Δ
internal/common/common_unitest_db.go	18.14% <100.00%> (ø)

... and 15 files with indirect coverage changes

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eliorerz, osherdp

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 [eliorerz,osherdp]

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

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 2585693 and 2 for PR HEAD 8888a5e in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 59ea056 and 1 for PR HEAD 8888a5e in total

[eliorerz]

/override ci/prow/edge-e2e-metal-assisted

[openshift-ci]

@eliorerz: Overrode contexts on behalf of eliorerz: ci/prow/edge-e2e-metal-assisted

In response to this:

/override ci/prow/edge-e2e-metal-assisted

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.

[openshift-ci]

@eliorerz: all tests passed!

Full PR test history. Your PR dashboard.

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.