Bug 1836149: Make it possible to configure the cluster waiting timeout. #212
Conversation
Since we look for nodes to be schedulable and sriov daemon's logs, depending on the environment this could take more than 10 minutes. Also, comment overlapping ranges test as it's always skipped as of today. Signed-off-by: Federico Paolinelli <fpaoline@redhat.com>
openshift-ci-robot
added
the
bugzilla/severity-unspecified
|
@fedepaol: This pull request references Bugzilla bug 1836149, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
In response to this:
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-robot
added
the
bugzilla/valid-bug
|
/lgtm |
|
@fedepaol: All pull requests linked via external trackers have merged: openshift/sriov-network-operator#212. Bugzilla bug 1836149 has been moved to the MODIFIED state. In response to this:
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. |
Since we look for nodes to be schedulable and sriov daemon's logs, depending on
the environment this could take more than 10 minutes.
That's amplified by the issue described in #200
This PR makes the waiting time (even) longer and also configurable.
Also, comment overlapping ranges test as it's always skipped as of today.