Increase timeout when creating PVC from snapshot in test test_pvc_snapshot

[jilju]

The PVC creation from snapshot took more time to reach Bound state. Increased the timeout to 180 seconds to avoid failure.
Test : tests/functional/pv/pvc_snapshot/test_pvc_snapshot.py::TestPvcSnapshot::test_pvc_snapshot
Fixes #11600

[jilju]

Verified: https://jenkins-csb-odf-qe-ocs4.dno.corp.redhat.com/job/qe-deploy-ocs-cluster/47732/

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jilju, petr-balogh, vavuthu

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

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

[petr-balogh]

@jilju please cherry-pick to lower release branches - the best will be till 4.14 please

[petr-balogh]

/cherry-pick release-4.17

[petr-balogh]

/cherry-pick release-4.16

[petr-balogh]

/cherry-pick release-4.15

[petr-balogh]

/cherry-pick release-4.14

[openshift-cherrypick-robot]

@petr-balogh: #11601 failed to apply on top of branch "release-4.15":

Applying: Increase timeout when creating PVC from snapshot in test test_pvc_snapshot
Using index info to reconstruct a base tree...
M	tests/functional/pv/pvc_snapshot/test_pvc_snapshot.py
Falling back to patching base and 3-way merge...
Auto-merging tests/functional/pv/pvc_snapshot/test_pvc_snapshot.py
CONFLICT (content): Merge conflict in tests/functional/pv/pvc_snapshot/test_pvc_snapshot.py
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 Increase timeout when creating PVC from snapshot in test test_pvc_snapshot

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.

[openshift-cherrypick-robot]

@petr-balogh: new pull request created: #11606

In response to this:

/cherry-pick release-4.17

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.

[openshift-cherrypick-robot]

@petr-balogh: new pull request created: #11607

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.

[openshift-cherrypick-robot]

@petr-balogh: #11601 failed to apply on top of branch "release-4.14":

Applying: Increase timeout when creating PVC from snapshot in test test_pvc_snapshot
Using index info to reconstruct a base tree...
A	tests/functional/pv/pvc_snapshot/test_pvc_snapshot.py
Falling back to patching base and 3-way merge...
Auto-merging tests/manage/pv_services/pvc_snapshot/test_pvc_snapshot.py
CONFLICT (content): Merge conflict in tests/manage/pv_services/pvc_snapshot/test_pvc_snapshot.py
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 Increase timeout when creating PVC from snapshot in test test_pvc_snapshot

In response to this:

/cherry-pick release-4.14

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.