Bug 1877261: UPSTREAM: 973: filesystem is not resized when restoring

[RomanBednar]

This is a cherry-pick of: kubernetes-sigs#972

Required for OCP 4.13: https://issues.redhat.com/browse/OCPBUGSM-17094

[RomanBednar]

/hold

The sanity tests are failing, same issue was discussed upstream and those tests got disabled as there is no simple fix yet. We need to disable them in Openshift as well.

openshift/release#36246

[openshift-ci]

@RomanBednar: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

• /test e2e-gcp
• /test e2e-gcp-csi
• /test images
• /test test

Use /test all to run all jobs.

In response to this:

/retest ci/prow/e2e-gcp

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]

@RomanBednar: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test e2e-gcp
• /test e2e-gcp-csi
• /test images
• /test test

Use /test all to run all jobs.

In response to this:

/test ci/prow/e2e-gcp

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.

[jsafrane]

/lgtm
/approve
/hold cancel
/override ci/prow/test

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jsafrane, RomanBednar

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 [jsafrane]

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

[openshift-ci]

@jsafrane: Overrode contexts on behalf of jsafrane: ci/prow/test

In response to this:

/lgtm
/approve
/hold cancel
/override ci/prow/test

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]

@RomanBednar: 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/test-infra repository. I understand the commands that are listed here.

[jsafrane]

/retitle Bug 1877261: UPSTREAM: 973: filesystem is not resized when restoring

[openshift-ci]

@RomanBednar: This pull request references Bugzilla bug 1877261, 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

• bug is open, matching expected state (open)
• bug target release (4.13.0) matches configured target release for branch (4.13.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

Requesting review from QA contact:
/cc @chao007

In response to this:

Bug 1877261: UPSTREAM: 973: filesystem is not resized when restoring

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]

@RomanBednar: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

• openshift/alibaba-cloud-csi-driver#23 is open

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 refresh.

Bugzilla bug 1877261 has not been moved to the MODIFIED state.

In response to this:

Bug 1877261: UPSTREAM: 973: filesystem is not resized when restoring

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.