Bug 1943804: increases the maximum time for migration for the encryption tests on AWS #1076
Conversation
|
@p0lyn0mial: This pull request references Bugzilla bug 1943804, which is valid. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: 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
bot
added
bugzilla/severity-urgent
|
/assign @sttts |
|
/test unit |
p0lyn0mial
force-pushed
the
encryption-test-wait-for-stable-revision
branch
3 times, most recently
from
896737b
to
52d5ce5
Compare
|
@p0lyn0mial: This pull request references Bugzilla bug 1943804, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
1 similar comment
|
@p0lyn0mial: This pull request references Bugzilla bug 1943804, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
…ecryption to complete observations: rolling out a single instance on AWS takes 3m 30s (max delay aws) + 60s (in-flight req) + 3m 10s (starting new instance - observation) = 7m 40s rolling out all instances on AWS 7m 40s * 3 = 23m a happy path scenario needs to roll out 3 revisions each taking 23m
p0lyn0mial
force-pushed
the
encryption-test-wait-for-stable-revision
branch
from
68c3da1
to
25baf46
Compare
p0lyn0mial
changed the title
|
@p0lyn0mial: This pull request references Bugzilla bug 1943804, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
1 similar comment
|
@p0lyn0mial: This pull request references Bugzilla bug 1943804, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: p0lyn0mial, sttts 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:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
|
@p0lyn0mial: Some pull requests linked via external trackers have merged: The following pull requests linked via external trackers have not merged: These pull request must merge or be unlinked from the Bugzilla bug in order for it to move to the next state. Once unlinked, request a bug refresh with Bugzilla bug 1943804 has not 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. |
In particular this PR:
properly detects if the tests are running in CI so that we get output with timeouts. Previously the output didn't have timestamps which made troubleshooting harder.
adds timestamps to logs to ease troubleshooting
increases the timeout for migration to 79 minutes:
xref: openshift/cluster-kube-apiserver-operator#1079