USHIFT-3270: Increase dnf low-bitrate timeout

[copejon]

No description provided.

[openshift-ci-robot]

@copejon: This pull request references USHIFT-3270 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.17.0" version, but no target version was set.

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 openshift-eng/jira-lifecycle-plugin repository.

[ggiguash]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: copejon, ggiguash

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 [copejon,ggiguash]

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 e9533cf and 2 for PR HEAD b753c6e in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 2cf0fbd and 1 for PR HEAD b753c6e in total

[openshift-ci]

@copejon: 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-sigs/prow repository. I understand the commands that are listed here.

[copejon]

/cherry-pick release-4.16

[openshift-cherrypick-robot]

@copejon: new pull request created: #3817

In response to this:

/cherry-pick release-4.16

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-sigs/prow repository.

[copejon]

/cherry-pick release-4.15

Nevermind. Another keyword in the file was renamed at some point after this patch, creating the merge conflict. Will have to submit a manual update

[openshift-cherrypick-robot]

@copejon: #3500 failed to apply on top of branch "release-4.15":

Applying: installing from the local repo can sometimes experience low transfer rates, which triggers an error message but is not fatal. since it's desirable to sometimes fail due to an error (just not this one), the best option is to give the transfer some extra time to recover
Using index info to reconstruct a base tree...
M	test/resources/microshift-rpm.resource
Falling back to patching base and 3-way merge...
Auto-merging test/resources/microshift-rpm.resource
CONFLICT (content): Merge conflict in test/resources/microshift-rpm.resource
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 installing from the local repo can sometimes experience low transfer rates, which triggers an error message but is not fatal. since it's desirable to sometimes fail due to an error (just not this one), the best option is to give the transfer some extra time to recover

In response to this:

/cherry-pick release-4.15

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-sigs/prow repository.