OCPBUGS-43625: Bump Azure Machine Timeout

[patrickdillon]

We're seeing sporadic cases of Azure control plane machines failing to provision. In some of those cases ignition pulling times out but eventually succeeds soon after the provisioning timeout fails, so we can try to alleviate this by bumping the azure timeout.

[openshift-ci-robot]

@patrickdillon: This pull request references Jira Issue OCPBUGS-43625, which is invalid:

• expected the bug to target the "4.18.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to [this](https://github.com/openshift/installer/pull/9226): >We're seeing sporadic cases of Azure control plane machines failing to provision. In some of those cases ignition pulling times out but eventually succeeds soon after the provisioning timeout fails, so we can try to alleviate this by bumping the azure timeout. Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Finstaller). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[patrickdillon]

/jira refresh

[openshift-ci-robot]

@patrickdillon: This pull request references Jira Issue OCPBUGS-43625, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

* bug is open, matching expected state (open) * bug target version (4.18.0) matches configured target version for branch (4.18.0) * bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact: /cc @jinyunma

In response to [this](https://github.com/openshift/installer/pull/9226#issuecomment-2489158741): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Finstaller). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[patrickdillon]

/retest

[openshift-ci[bot]]

@patrickdillon: 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/e2e-azurestack	98320a6f39acdb2fec4008325eadc22c8fa7cc59	link	false	/test e2e-azurestack

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).

[sadasu]

/approve

I encounter this pretty often while testing locally.

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sadasu

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](https://github.com/openshift/installer/blob/master/OWNERS)~~ [sadasu] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[patrickdillon]

/label acknowledge-critical-fixes-only

[patrickdillon]

CI logs show the timeout was increased:

time="2024-11-20T22:24:17Z" level=info msg="Waiting up to 20m0s (until 10:44PM UTC) for machines [ci-op-lrqqv1pv-0844b-tbnjg-bootstrap ci-op-lrqqv1pv-0844b-tbnjg-master-0 ci-op-lrqqv1pv-0844b-tbnjg-master-1 ci-op-lrqqv1pv-0844b-tbnjg-master-2] to provision..."

[rna-afk]

/lgtm

[openshift-ci-robot]

@patrickdillon: Jira Issue OCPBUGS-43625: All pull requests linked via external trackers have merged:

• openshift/installer#9226

Jira Issue OCPBUGS-43625 has been moved to the MODIFIED state.

In response to [this](https://github.com/openshift/installer/pull/9226): >We're seeing sporadic cases of Azure control plane machines failing to provision. In some of those cases ignition pulling times out but eventually succeeds soon after the provisioning timeout fails, so we can try to alleviate this by bumping the azure timeout. Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Finstaller). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-altinfra This PR has been included in build ose-installer-altinfra-container-v4.18.0-202411220907.p0.g0432739.assembly.stream.el9. All builds following this will include this PR.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-terraform-providers This PR has been included in build ose-installer-terraform-providers-container-v4.18.0-202411220907.p0.g0432739.assembly.stream.el9. All builds following this will include this PR.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: ose-baremetal-installer This PR has been included in build ose-baremetal-installer-container-v4.18.0-202411220907.p0.g0432739.assembly.stream.el9. All builds following this will include this PR.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-artifacts This PR has been included in build ose-installer-artifacts-container-v4.18.0-202411220907.p0.g0432739.assembly.stream.el9. All builds following this will include this PR.