-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Bug 2061947: IBMCloud: Handle missing RG #6152
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
|
@cjschaef: This pull request references Bugzilla bug 2061947, 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
Requesting review from QA contact: 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. |
|
Tested that an empty |
|
can you help deal with such issue, fail to delete the volume (blocked by Service Broker returned error status code 500) , avoid loop prompt. {"clusterName":"logci4315","clusterID":"211f8ae0-bd1a-4b81-a0e3-3db827a6a5f6","infraID":"logci4315-hxxvx","ibmcloud":{"accountID":"fdc2e14cf8bc4d53a67f972dc2e2c861","baseDomain":"ibmcloud.qe.devcluster.openshift.com","cisInstanceCRN":"crn:v1:bluemix:public:internet-svcs:global:a/fdc2e14cf8bc4d53a67f972dc2e2c861:e8ee6ca1-4b31-4307-8190-e67f6925f83b::","region":"us-east","resourceGroupName":"logci4315-hxxvx"}} |
|
/retest |
|
/test e2e-ibmcloud |
|
Slightly concerning on the recent May have been an issue with IBM Cloud API's (outage), but will look for a more serious issue in case the IAM policies that have been setup have been corrupted/changed. |
|
Things appear okay, will attempt to retry test, given other CI builds don't seem affected a this time. |
|
There have been numerous issues with IBM Cloud IAM and COS. I believe that is the cause of the latest failure (perhaps earlier failure as well), I have experienced with local testing. I will monitor until things appear to be restored and retry the testing then. |
|
/label qe-approved |
|
@MayXuQQ: This pull request references Bugzilla bug 2061947, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
|
I've been seeing IAM errors with IBM Cloud, causing COS and other failures, likely resulting in the issues during testing. /test e2e-ibmcloud |
|
/test e2e-ibmcloud |
|
|
|
MAPI patch merged. Retesting |
|
This This should be good for review/merge finally. |
|
/cc @rvanderp3 |
Handle cases when there is no ResourceGroupName provided during destroy, or the ResourceGroup doesn't exist, or cannot be found. Related: https://bugzilla.redhat.com/show_bug.cgi?id=2061947
|
/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 DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
|
/retest-required |
|
@cjschaef: 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. |
|
@cjschaef: All pull requests linked via external trackers have merged: Bugzilla bug 2061947 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. |
Handle cases when there is no ResourceGroupName provided
during destroy, or the ResourceGroup doesn't exist, or cannot
be found.
Related: https://bugzilla.redhat.com/show_bug.cgi?id=2061947