Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-9120

[IPI on Alibabacloud] Destroy of 100 worker nodes on alibaba fails to get instance ids

    • Quality / Stability / Reliability
    • None
    • None
    • None
    • Moderate
    • None
    • Unspecified
    • None
    • None
    • Rejected
    • None
    • None
    • If docs needed, set a value
    • None
    • None
    • None
    • None
    • None

      Thanks for opening a bug report!
      Before hitting the button, please fill in as much of the template below as you can.
      If you leave out information, it's harder to help you.
      Be ready for follow-up questions, and please respond in a timely manner.
      If we can't reproduce a bug we might close your issue.
      If we're wrong, PLEASE feel free to reopen it and explain why.

      Version:

      $ openshift-install version
      4.10.0-0.nightly-2022-02-11-123954

      Platform: Alibaba

      #Please specify the platform type: aws, libvirt, openstack or baremetal etc.

      Please specify: IPI

      • IPI (automated install with `openshift-install`. If you don't know, then it's IPI)
      • UPI (semi-manual installation on customized infrastructure)

      What happened?
      During destroy of a cluster created on the alibaba cloud type, if there are over 100 worker nodes, the destroy cluster is not able to find InstanceIds because of not having the invalid parameter

      ~/openshift-install destroy cluster --dir . --log-level=debug
      DEBUG OpenShift Installer 4.10.0-0.nightly-2022-01-24-070025
      DEBUG Built from commit 716cf76f4567251287d0fa42d372981e9a37c0ab
      DEBUG Retrieving cloud resources tags=

      {"kubernetes.io/cluster/qe-pr-al3-qm5qc":"owned"}

      DEBUG Retrieving cloud resources tags=

      {"ack.aliyun.com":"qe-pr-al3-qm5qc"}

      DEBUG Searching DNS records stage=DNS records
      DEBUG Searching RAM policy policyName=qe-pr-al3-qm5qc-policy-bootstrap stage=RAM roles
      DEBUG Searching OSS bucket bucketName=qe-pr-al3-qm5qc-image-registry-us-east-1-emunisbqlmryqmbnrvmce stage=OSS buckets
      DEBUG Unbinding tags for OSS bucket bucketName=qe-pr-al3-qm5qc-image-registry-us-east-1-emunisbqlmryqmbnrvmce stage=OSS buckets tags=[kubernetes.io/cluster/qe-pr-al3-qm5qc]
      DEBUG Error executing stage error=SDK.ServerError
      ErrorCode: InvalidParameter
      Recommend: https://error-center.aliyun.com/status/search?Keyword=InvalidParameter&source=PopGw
      RequestId: 390C1C51-60BC-3AB5-872E-38B064D3DCEB
      Message: The specified parameter "InstanceIds" is not valid. stage=ECS instances
      DEBUG Deleting policyName=qe-pr-al3-qm5qc-policy-bootstrap stage=RAM roles
      DEBUG Searching OSS bucket objects bucketName=qe-pr-al3-qm5qc-image-registry-us-east-1-emunisbqlmryqmbnrvmce stage=OSS buckets
      DEBUG Deleting OSS bucket bucketName=qe-pr-al3-qm5qc-image-registry-us-east-1-emunisbqlmryqmbnrvmce stage=OSS buckets
      DEBUG Deleting roleName=qe-pr-al3-qm5qc-role-bootstrap stage=RAM roles
      DEBUG Searching RAM policy policyName=qe-pr-al3-qm5qc-policy-master stage=RAM roles
      DEBUG Public DNS records deleted stage=DNS records
      DEBUG Deleting policyName=qe-pr-al3-qm5qc-policy-master stage=RAM roles
      DEBUG Deleting roleName=qe-pr-al3-qm5qc-role-master stage=RAM roles
      DEBUG Searching RAM policy policyName=qe-pr-al3-qm5qc-policy-worker stage=RAM roles
      DEBUG Deleting policyName=qe-pr-al3-qm5qc-policy-worker stage=RAM roles
      INFO OSS bucket deleted bucketName=qe-pr-al3-qm5qc-image-registry-us-east-1-emunisbqlmryqmbnrvmce stage=OSS buckets
      INFO OSS buckets deleted stage=OSS buckets
      DEBUG Deleting roleName=qe-pr-al3-qm5qc-role-worker stage=RAM roles
      INFO RAM roles deleted stage=RAM roles
      DEBUG Error executing stage error=SDK.ServerError
      ErrorCode: InvalidParameter
      Recommend: https://error-center.aliyun.com/status/search?Keyword=InvalidParameter&source=PopGw
      RequestId: 497E6B29-59C7-325F-8EBC-61FCF95E9A70
      Message: The specified parameter "InstanceIds" is not valid. stage=ECS instances
      DEBUG Error executing stage error=SDK.ServerError
      ErrorCode: InvalidParameter
      Recommend: https://error-center.aliyun.com/status/search?Keyword=InvalidParameter&source=PopGw
      RequestId: A599735E-6AF2-333F-B754-54EE928AD7CC
      Message: The specified parameter "InstanceIds" is not valid. stage=ECS instances
      DEBUG Error executing stage error=SDK.ServerError
      ErrorCode: InvalidParameter
      Recommend: https://error-center.aliyun.com/status/search?Keyword=InvalidParameter&source=PopGw
      RequestId: FD02FACF-F274-34F8-A2A4-1B8DEB7DFE3D
      Message: The specified parameter "InstanceIds" is not valid. stage=ECS instances
      DEBUG Error executing stage error=SDK.ServerError
      ErrorCode: InvalidParameter
      Recommend: https://error-center.aliyun.com/status/search?Keyword=InvalidParameter&source=PopGw
      RequestId: 0B4C116E-5472-3AB5-9584-92CF3AF7C6FD
      Message: The specified parameter "InstanceIds" is not valid. stage=ECS instances

      What did you expect to happen?
      The destroy to fully cleanup all instances associated with the cluster and other cloud specific resources

      How to reproduce it (as minimally and precisely as possible)?

      Create an openshift cluster on alibaba, scale the cluster to have over 100 worker nodes (console or cli)
      Once all worker nodes go to the ready state

      $ openshift-install destroy cluster
      ... error seen

              bteng@redhat.com Bo Teng (Inactive)
              prubenda Paige Patton
              Jianli Wei Jianli Wei
              Red Hat Employee
              Jianli Wei
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: