Bug 2090816: Increase bootstrap timeout, not k8s API timeout

[honza]

This fixes a previous change where we mistakenly increased the
Kubernetes API timeout instead of the bootstrap timeout.

[openshift-ci]

@honza: This pull request references Bugzilla bug 2090816, which is invalid:

• expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is MODIFIED instead

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

In response to this:

Bug 2090816: Increase bootstrap timeout, not k8s API timeout

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.

[honza]

/bugzilla refresh

[openshift-ci]

@honza: This pull request references Bugzilla bug 2090816, 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.11.0) matches configured target release for branch (4.11.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 @awolffredhat

In response to this:

/bugzilla refresh

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.

[derekhiggins]

/lgtm
from the metal-ipi job

level=debug msg=Built from commit 83211d26348738777578d6459ca2dee6cc6e4726
level=info msg=Waiting up to 20m0s (until 3:53PM) for the Kubernetes API at https://api.ostest.test.metalkube.org:6443...
...
level=info msg=Waiting up to 1h0m0s (until 4:33PM) for bootstrapping to complete...

[sdodson]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sdodson

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

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

[openshift-ci]

@honza: The following tests 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-metal-ipi	e4f7e09	link	false	/test e2e-metal-ipi
ci/prow/e2e-libvirt	e4f7e09	link	false	/test e2e-libvirt
ci/prow/e2e-ibmcloud	e4f7e09	link	false	/test e2e-ibmcloud
ci/prow/e2e-crc	e4f7e09	link	false	/test e2e-crc

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.

[openshift-ci]

@honza: All pull requests linked via external trackers have merged:

• openshift/installer#5981
• openshift/installer#6010

Bugzilla bug 2090816 has been moved to the MODIFIED state.

In response to this:

Bug 2090816: Increase bootstrap timeout, not k8s API timeout

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.

[honza]

/cherrypick release-4.10

[openshift-cherrypick-robot]

@honza: #6010 failed to apply on top of branch "release-4.10":

Applying: Increase bootstrap timeout, not k8s API timeout
Using index info to reconstruct a base tree...
M	cmd/openshift-install/create.go
Falling back to patching base and 3-way merge...
Auto-merging cmd/openshift-install/create.go
CONFLICT (content): Merge conflict in cmd/openshift-install/create.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Increase bootstrap timeout, not k8s API timeout
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick release-4.10

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.

[naumvd95]

Hello folks! @honza @derekhiggins, wanted to pay your attention that the higher timeout needed not only for

// Name is the name for the baremetal platform.
const Name string = "baremetal"

but for all platforms where BM instances used. AFAIU its +1 extra case at the current moment - its AWS metal instances. And that's exact our problem =(

#7326

It would be awesome if you find some time to provide a fix for such case :)

thanks in advance and have a great day!