azure: avoid timeouts due to growfs

[r4f4]

Using the workaround in [1] until the issue is fixed in RHCOS.

[1] coreos/fedora-coreos-tracker#1183 (comment)

[r4f4]

/test e2e-azure-ovn

[patrickdillon]

@r4f4 what about adding to control plane nodes too?

@jlebon wonder if you could ptal

[openshift-ci]

@r4f4: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/okd-scos-e2e-aws-ovn	813eb77	link	false	/test okd-scos-e2e-aws-ovn

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.

[jlebon]

/approve

It looks fine to me. Just to be clear though, this is only required for very large disks. Not sure on how conditionalized this code path here is/needs to be based on that. (I vaguely recall that on Azure we always provision 1T disks to get the higher IOPS tier? If that's the case, then this is fine.)

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jlebon
Once this PR has been reviewed and has the lgtm label, please ask for approval from r4f4. For more information see the Kubernetes Code Review Process.

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

[r4f4]

There is an alternative implementation with a separate /var partition at #9310

[r4f4]

/close

I'm going to close this in favor of #9310. If 9310 ends up not being the way forward, we can reopen this PR.

[openshift-ci]

@r4f4: Closed this PR.

In response to this:

/close

I'm going to close this in favor of #9310. If 9310 ends up not being the way forward, we can reopen this PR.

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.