Failure when provisioning the first Data Disk after creating MCIS

[yunkon-kim]

This is an issue to share the current situation first.

What happened
: I encountered an error when I created and attached a Data Disk to an MCIS only for the first time.
: No issues in the following cases:

• When I created the 2nd Data Disk and attached it to the 2nd VM
• When I force detached and deleted the 1st failure Data Disk, and then created a new Data Disk and attached it to the 1st VM

How to reproduce it (as minimally and precisely as possible)
: (Tested this 3 times)
: The situation could be reproduced by the following steps

• Create an MCIS on ap-northeast-2 with 3 nodes
• Call POST /ns/{nsId}/mcis/{mcisId}/vm/{vmId}/dataDisk
  • nsId: demo-ns01
  • mcisId: mc-m77fy
  • vmId: g1-1
  • ReqeustBody:

    {
      "description": "test-dd01",
      "diskSize": "77",
      "diskType": "default",
      "name": "aws-ap-northeast-2-datadisk01"
    }

• Tumblebug logs

7:55PM INF core/mcir/datadisk.go:264 > PUT CreateDataDisk
7:55PM ERR core/common/client.go:125 > Type assertion failed for cache item: expected CacheItem[mcis.SpiderVMInfo], got common.CacheItem[github.com/cloud-barista/cb-tumblebug/src/core/mcis.statusResponse·7]
7:55PM ERR core/mcis/manageInfo.go:1558 > error="type assertion failed for cache item"
7:55PM ERR core/mcis/manageInfo.go:1414 > error="type assertion failed for cache item"
7:55PM ERR core/mcis/manageInfo.go:1504 > error="[Error from: http://localhost:1024/spider/disk/demo-ns01-aws-ap-northeast-2-datadisk01/attach] Status code: 500 Internal Server Error, Message: {\"message\":\"VolumeInUse: vol-030909a938fea49a0 is already attached to an instance\\n\\tstatus code: 400, request id: 582ab3ae-f238-49a4-8769-2b291891be04\"}\n"
7:55PM ERR core/mcis/manageInfo.go:1414 > error="[Error from: http://localhost:1024/spider/disk/demo-ns01-aws-ap-northeast-2-datadisk01/attach] Status code: 500 Internal Server Error, Message: {\"message\":\"VolumeInUse: vol-030909a938fea49a0 is already attached to an instance\\n\\tstatus code: 400, request id: 582ab3ae-f238-49a4-8769-2b291891be04\"}\n"
7:55PM ERR core/mcis/manageInfo.go:1504 > error="[Error from: http://localhost:1024/spider/disk/demo-ns01-aws-ap-northeast-2-datadisk01/attach] Status code: 500 Internal Server Error, Message: {\"message\":\"VolumeInUse: vol-030909a938fea49a0 is already attached to an instance\\n\\tstatus code: 400, request id: c5767115-012f-4a17-bffb-845784dfab72\"}\n"
7:55PM ERR core/mcis/manageInfo.go:1414 > error="[Error from: http://localhost:1024/spider/disk/demo-ns01-aws-ap-northeast-2-datadisk01/attach] Status code: 500 Internal Server Error, Message: {\"message\":\"VolumeInUse: vol-030909a938fea49a0 is already attached to an instance\\n\\tstatus code: 400, request id: c5767115-012f-4a17-bffb-845784dfab72\"}\n"

• Spider logs

VolumeInUse: vol-030909a938fea49a0 is already attached to an instance
        status code: 400, request id: 582ab3ae-f238-49a4-8769-2b291891be04
[CB-SPIDER].[ERROR]: 2024-06-17 10:55:30 DiskHandler.go:406, github.com/cloud-barista/cb-spider/cloud-control-manager/cloud-driver/drivers/aws/resources.(*AwsDiskHandler).AttachDisk() - VolumeInUse: vol-030909a938fea49a0 is already attached to an instance
        status code: 400, request id: 582ab3ae-f238-49a4-8769-2b291891be04
[HISCALL].[129.254.75.33] 2024-06-17 10:55:30 (Monday) github.com/cloud-barista/cb-spider/cloud-control-manager/cloud-driver/drivers/aws/resources.LoggingError():74 - "CloudOS" : "AWS", "RegionZone" : "ap-northeast-2", "ResourceType" : "DISK", "ResourceName" : "demo-ns01-aws-ap-northeast-2-datadisk01-cpo1c1fm9p40l4rgubv0", "CloudOSAPI" : "AttachDisk()", "ElapsedTime" : "0.3493", "ErrorMSG" : "VolumeInUse: vol-030909a938fea49a0 is already attached to an instance
        status code: 400, request id: 582ab3ae-f238-49a4-8769-2b291891be04"
[CB-SPIDER].[ERROR]: 2024-06-17 10:55:30 DiskManager.go:516, github.com/cloud-barista/cb-spider/api-runtime/common-runtime.AttachDisk() - VolumeInUse: vol-030909a938fea49a0 is already attached to an instance
        status code: 400, request id: 582ab3ae-f238-49a4-8769-2b291891be04
[CB-SPIDER].[ERROR]: 2024-06-17 10:55:35 DiskHandler.go:406, github.com/cloud-barista/cb-spider/cloud-control-manager/cloud-driver/drivers/aws/resources.(*AwsDiskHandler).AttachDisk() - VolumeInUse: vol-030909a938fea49a0 is already attached to an instance
        status code: 400, request id: c5767115-012f-4a17-bffb-845784dfab72
[HISCALL].[129.254.75.33] 2024-06-17 10:55:35 (Monday) github.com/cloud-barista/cb-spider/cloud-control-manager/cloud-driver/drivers/aws/resources.LoggingError():74 - "CloudOS" : "AWS", "RegionZone" : "ap-northeast-2", "ResourceType" : "DISK", "ResourceName" : "demo-ns01-aws-ap-northeast-2-datadisk01-cpo1c1fm9p40l4rgubv0", "CloudOSAPI" : "AttachDisk()", "ElapsedTime" : "0.2377", "ErrorMSG" : "VolumeInUse: vol-030909a938fea49a0 is already attached to an instance
        status code: 400, request id: c5767115-012f-4a17-bffb-845784dfab72"
[CB-SPIDER].[ERROR]: 2024-06-17 10:55:35 DiskManager.go:516, github.com/cloud-barista/cb-spider/api-runtime/common-runtime.AttachDisk() - VolumeInUse: vol-030909a938fea49a0 is already attached to an instance
        status code: 400, request id: c5767115-012f-4a17-bffb-845784dfab72
VolumeInUse: vol-030909a938fea49a0 is already attached to an instance
        status code: 400, request id: c5767115-012f-4a17-bffb-845784dfab72

Anything else we need to know?
: v0.8.14 encountered a panic by type assertion failure on ExecuteHttpRequest and ResponseBodyDump
: A PR for this will be opened soon

Environment

• Source version or branch:
  • Tumblebug v0.8.14 (build source code and run it)
  • Spider v0.8.18 (container)
  • MapUI v0.8.19 (container)
• OS: Ubuntu 22.04 (on WSL2)