[bug] Cloudcontrol on networkmanager core network with empty policy will hang

0

There seems to be a bug when you pass an empty policy to cloudcontrol to update your corenetwork in networkmanager. You can replicate this with the cli.

When you pass in a patch document of "[]" it immediately returns success, then when you query the request, it is stuck in pending. You can replicate this with cli:

aws cloudcontrol update-resource --type-name AWS::NetworkManager::CoreNetwork --identifier core-network-xxxxx --patch-document "[]"

{
    "ProgressEvent": {
        "TypeName": "AWS::NetworkManager::CoreNetwork",
        "Identifier": "core-network-xxxxx",
        "RequestToken": "23xxxxx07",
        "Operation": "UPDATE",
        "OperationStatus": "SUCCESS",
        ...
        

aws cloudcontrol get-resource-request-status --request-token 23xxxxx07

{
    "ProgressEvent": {
        "TypeName": "AWS::NetworkManager::CoreNetwork",
        "RequestToken": "23xxxxx07",
        "OperationStatus": "PENDING",
        "EventTime": "2022-09-07T16:39:46.821000+00:00"
    }
}

Its stuck in pending and did not resolve after days. There are no changes/updates reflected in network manager.

EDIT: looks like this issue occurs when "[]" is passed to NetworkManager::VpcAttachment

Avedis
질문됨 2년 전128회 조회
답변 없음

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠