We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Let's make things better!
A clear and concise description of what the bug is. Stack cannot be deleted in public clouds
If the bug is related a CI job, put the job information below:
2019-01-22 22:32:57.487189 | TASK [Clean up resources of openshift cluster on opentelekomcloud] 2019-01-22 22:32:57.905869 | ubuntu-xenial | + openstack stack delete --wait --yes openshift-2ae38ab46b.openlab.com 2019-01-22 22:33:05.961098 | ubuntu-xenial | Unable to delete 1 of the 1 stacks. 2019-01-22 22:33:05.961557 | ubuntu-xenial | 2019-01-22 22:33:00.074489 [openshift-2ae38ab46b.openlab.com]: DELETE_IN_PROGRESS Stack DELETE started 2019-01-22 22:33:05.961661 | ubuntu-xenial | 2019-01-22 22:33:00.114413 [openshift-2ae38ab46b.openlab.com.infra_nodes]: DELETE_IN_PROGRESS state changed 2019-01-22 22:33:05.961744 | ubuntu-xenial | 2019-01-22 22:33:00.201994 [openshift-2ae38ab46b.openlab.com.masters]: DELETE_IN_PROGRESS state changed 2019-01-22 22:33:05.961827 | ubuntu-xenial | 2019-01-22 22:33:00.306974 [openshift-2ae38ab46b.openlab.com.compute_nodes]: DELETE_IN_PROGRESS state changed 2019-01-22 22:33:05.961907 | ubuntu-xenial | 2019-01-22 22:33:00.406842 [openshift-2ae38ab46b.openlab.com.cns]: DELETE_IN_PROGRESS state changed 2019-01-22 22:33:05.961986 | ubuntu-xenial | 2019-01-22 22:33:00.459140 [openshift-2ae38ab46b.openlab.com.etcd]: DELETE_IN_PROGRESS state changed 2019-01-22 22:33:05.962067 | ubuntu-xenial | 2019-01-22 22:33:00.517229 [openshift-2ae38ab46b.openlab.com.infra_nodes]: DELETE_COMPLETE state changed 2019-01-22 22:33:05.962141 | ubuntu-xenial | 2019-01-22 22:33:00.548818 [openshift-2ae38ab46b.openlab.com.cns]: DELETE_COMPLETE state changed 2019-01-22 22:33:05.962224 | ubuntu-xenial | 2019-01-22 22:33:00.581801 [openshift-2ae38ab46b.openlab.com.infra-secgrp]: DELETE_IN_PROGRESS state changed 2019-01-22 22:33:05.962356 | ubuntu-xenial | 2019-01-22 22:33:01.079908 [openshift-2ae38ab46b.openlab.com.infra-secgrp]: DELETE_FAILED EndpointNotFound: resources.infra-secgrp: internalURL endpoint for vpc service in eu-de region not found 2019-01-22 22:33:05.962438 | ubuntu-xenial | 2019-01-22 22:33:01.094126 [openshift-2ae38ab46b.openlab.com.compute_nodes]: DELETE_FAILED DELETE aborted 2019-01-22 22:33:05.962569 | ubuntu-xenial | 2019-01-22 22:33:01.109008 [openshift-2ae38ab46b.openlab.com.masters]: DELETE_FAILED DELETE aborted 2019-01-22 22:33:05.962649 | ubuntu-xenial | 2019-01-22 22:33:01.124679 [openshift-2ae38ab46b.openlab.com.etcd]: DELETE_FAILED DELETE aborted 2019-01-22 22:33:05.962786 | ubuntu-xenial | 2019-01-22 22:33:01.143818 [openshift-2ae38ab46b.openlab.com]: DELETE_FAILED Resource DELETE failed: EndpointNotFound: resources.infra-secgrp: internalURL endpoint for vpc service in eu-de region not found
Describe how to reproduce the issue:
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Temporarily disable openshift job because of resource cleanup failure
12e9b8b
Related: # theopenlab/openlab#178
Temporarily disable openshift job because of resource cleanup failure (…
095ee0a
…#425) Related-Bug: theopenlab/openlab#178
We do not run these testing now, closed
Sorry, something went wrong.
liusheng
No branches or pull requests
Let's make things better!
Describe the bug
A clear and concise description of what the bug is.
Stack cannot be deleted in public clouds
Related Job information
If the bug is related a CI job, put the job information below:
openshift-origin-functional-test-opentelekomcloud
http://logs.openlabtesting.org/logs/periodic-2/github.com/huaweicloud/openshift-ansible/master/openshift-origin-functional-test-opentelekomcloud/2ae38ab/job-output.txt.gz
Steps to reproduce the issue
Describe how to reproduce the issue:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: