-
Notifications
You must be signed in to change notification settings - Fork 1.4k
OCPBUGS-47652: IBMCloud: Set CAPI boot volumes #9385
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
IBM Cloud CAPI machine boot volumes must have a size set, for now default to 100 GB, until an option is available to configure the size is available via the machinepool. Related: https://issues.redhat.com/browse/OCPBUGS-47652
@cjschaef: This pull request references Jira Issue OCPBUGS-47652, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In 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 openshift-eng/jira-lifecycle-plugin repository. |
/test altinfra-e2e-ibmcloud-capi-ovn |
I will try retesting, using BYOK along with BYON support, to see if I can duplicate the failure locally.
For example, I'd like to see the machine manifest, which contains this:
Before I hack up something to debug more, I'll run local testing with BYOK and BYON together to see if I can duplicate the failure. |
No joy in recreating locally. I'd like to see what a retrigger does before I begin modifying content to try to parse out why the CI is failing. /test altinfra-e2e-ibmcloud-capi-ovn |
Ah, shoot. That was not a build from this PR. |
pre-merge build create byo-kms cluster succeed. |
/retest |
/test altinfra-e2e-ibmcloud-capi-ovn |
@cjschaef: The following tests failed, say
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. |
/jira refresh |
@MayXuQQ: This pull request references Jira Issue OCPBUGS-47652, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: In 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 openshift-eng/jira-lifecycle-plugin repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pre-merge test PASS
/test altinfra-e2e-ibmcloud-capi-ovn |
/label qe-approved |
@cjschaef: This pull request references Jira Issue OCPBUGS-47652, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: In 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 openshift-eng/jira-lifecycle-plugin repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pre-merge install PASS
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: MayXuQQ, patrickdillon 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:
Approvers can indicate their approval by writing |
efbd044
into
openshift:main
@cjschaef: Jira Issue OCPBUGS-47652: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-47652 has been moved to the MODIFIED state. In 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 openshift-eng/jira-lifecycle-plugin repository. |
IBM Cloud CAPI machine boot volumes must have a size set, for now default to 100 GB, until an option is available to configure the size is available via the machinepool.
Related: https://issues.redhat.com/browse/OCPBUGS-47652