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
What would you like to be enhanced : 리소스 조회에서 특정리소스에 문제가 있더라도 state로 비정상표시 후 목록조회는 되어야 함.
Why is this needed : 데이터 디스크 조회 중 등록된 리소스가 비정상적인 경우 목록조회가 되지 않음.
Proposed solution : getResource에서 error 시 ListResource에서는 해당 row만 error로 인식되도록 하고 남은 resource를 조회하도록 변경 요망
아래 로그에서 GCP 항목까지 조회 되다가 tencent에서 오류가 나면서 search failed 를 return.
...GCP [Check resource] dataDisk, cortado-window-test-gcp-my-win-1-cdthruh6to9ur0mung0g-disk-0 [Get resource] dataDisk, cortado-window-test-gcp-my-win-1-cdthruh6to9ur0mung0g-disk-0 HTTP Status code: 200 res.Status: Available in UpdateResourceObject; extracted resourceId: cortado-window-test-gcp-my-win-1-cdthruh6to9ur0mung0g-disk-0 [Check resource] dataDisk, cortado-window-test-gcp-my-win-1-cdthruh6to9ur0mung0g-disk-1 [Get resource] dataDisk, cortado-window-test-gcp-my-win-1-cdthruh6to9ur0mung0g-disk-1 HTTP Status code: 200 res.Status: Available in UpdateResourceObject; extracted resourceId: cortado-window-test-gcp-my-win-1-cdthruh6to9ur0mung0g-disk-1 [Check resource] dataDisk, gcp-disk-1 [Get resource] dataDisk, gcp-disk-1 HTTP Status code: 200 res.Status: Attached in UpdateResourceObject; extracted resourceId: gcp-disk-1 [Check resource] dataDisk, gcp-disk-2 [Get resource] dataDisk, gcp-disk-2 HTTP Status code: 200 res.Status: Attached in UpdateResourceObject; extracted resourceId: gcp-disk-2 ... tencent [Check resource] dataDisk, ten-disk-1 [Get resource] dataDisk, ten-disk-1 HTTP Status code: 500 body: {"message":"search failed"}
The text was updated successfully, but these errors were encountered:
@dogfootman 버그 리포트 감사합니다! :) 해당 사항은 #1295 를 통해 해결하였고,
https://github.com/cloud-barista/cb-tumblebug/releases/tag/v0.7.3 으로 프리릴리스하였습니다.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
What would you like to be enhanced
: 리소스 조회에서 특정리소스에 문제가 있더라도 state로 비정상표시 후 목록조회는 되어야 함.
Why is this needed
: 데이터 디스크 조회 중 등록된 리소스가 비정상적인 경우 목록조회가 되지 않음.
Proposed solution
: getResource에서 error 시 ListResource에서는 해당 row만 error로 인식되도록 하고 남은 resource를 조회하도록 변경 요망
목록조회시 search failed로 500 error return
--
[CLOUD-BARISTA].[ERROR]: 2023-02-20 23:32:29 common.go:1420, github.com/cloud-barista/cb-tumblebug/src/core/mcir.GetResource() - {"message":"search failed"}
[CLOUD-BARISTA].[ERROR]: 2023-02-20 23:32:29 common.go:1015, github.com/cloud-barista/cb-tumblebug/src/core/mcir.ListResource() - {"message":"search failed"}
아래 로그에서 GCP 항목까지 조회 되다가 tencent에서 오류가 나면서 search failed 를 return.
...GCP
[Check resource] dataDisk, cortado-window-test-gcp-my-win-1-cdthruh6to9ur0mung0g-disk-0
[Get resource] dataDisk, cortado-window-test-gcp-my-win-1-cdthruh6to9ur0mung0g-disk-0
HTTP Status code: 200
res.Status: Available
in UpdateResourceObject; extracted resourceId: cortado-window-test-gcp-my-win-1-cdthruh6to9ur0mung0g-disk-0
[Check resource] dataDisk, cortado-window-test-gcp-my-win-1-cdthruh6to9ur0mung0g-disk-1
[Get resource] dataDisk, cortado-window-test-gcp-my-win-1-cdthruh6to9ur0mung0g-disk-1
HTTP Status code: 200
res.Status: Available
in UpdateResourceObject; extracted resourceId: cortado-window-test-gcp-my-win-1-cdthruh6to9ur0mung0g-disk-1
[Check resource] dataDisk, gcp-disk-1
[Get resource] dataDisk, gcp-disk-1
HTTP Status code: 200
res.Status: Attached
in UpdateResourceObject; extracted resourceId: gcp-disk-1
[Check resource] dataDisk, gcp-disk-2
[Get resource] dataDisk, gcp-disk-2
HTTP Status code: 200
res.Status: Attached
in UpdateResourceObject; extracted resourceId: gcp-disk-2
... tencent
[Check resource] dataDisk, ten-disk-1
[Get resource] dataDisk, ten-disk-1
HTTP Status code: 500
body: {"message":"search failed"}
The text was updated successfully, but these errors were encountered: