Bug 2046181: baremetal: reduce API timeout to 15 minutes #5639
Conversation
There is no point in waiting 1 hours for Ironic API to start: even given the bootstrap VM start-up, it takes much less. Currently, users have to wait 1 hour to learn that API failed to start for some reason (e.g. because the network config has an error).
openshift-ci
bot
added
the
bugzilla/severity-medium
|
@dtantsur: This pull request references Bugzilla bug 2046181, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Bugzilla (yporagpa@redhat.com), skipping review request. DetailsIn response to this:
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
bot
added
the
bugzilla/valid-bug
|
This seems reasonable to me, but I think long term we need a better way to indicate success/failure of services on the bootstrap VM. I know @staebler did some work on that for bootkube ref #4742 - we could do similar for the ironic services for more granular reporting of what actually failed, but AFAICS that only helps with the bootstrap gather reporting. Also cc @kirankt as I know you're familiar with this and may have some suggestions for the long term direction here - ideally I think we need some way to tell the user if any service is constantly failing/restarting on the bootstrap VM, but I'm unclear what the feedback path from bootstrap->installer should look like. |
openshift-ci
bot
added
platform/baremetal
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hardys, kirankt The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
13 similar comments
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/test e2e-metal-ipi-virtualmedia |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
@dtantsur: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
@dtantsur: All pull requests linked via external trackers have merged: Bugzilla bug 2046181 has been moved to the MODIFIED state. DetailsIn response to this:
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. |
5 participants
There is no point in waiting 1 hours for Ironic API to start: even given
the bootstrap VM start-up, it takes much less. Currently, users have to
wait 1 hour to learn that API failed to start for some reason (e.g.
because the network config has an error).