route: increasing route timeout to 5min (PROJQUAY-2679) #825
Conversation
|
Is 5m a valid input, or do we need 300s? Otherwise LGTM |
|
Testing with |
bcaton85
force-pushed
the
PROJQUAY-2679
branch
2 times, most recently
from
8ea2014
to
c9de582
Compare
- Increasing route timeout
bcaton85
force-pushed
the
PROJQUAY-2679
branch
from
c9de582
to
e189f89
Compare
|
/cherry-pick redhat-3.9 |
|
/cherrypick redhat-3.9 |
|
@bcaton85: new pull request created: #827 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. |
|
@bcaton85: new pull request could not be created: failed to create pull request against quay/quay-operator#redhat-3.9 from head openshift-cherrypick-robot:cherry-pick-825-to-redhat-3.9: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for openshift-cherrypick-robot:cherry-pick-825-to-redhat-3.9."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request"} 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. |
Pushes to IBM storage fail for larger image layers (10gb) due to timeout of the route.