• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • ACS Cloud Service
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      ./stage-action.sh admin-get-tenant d4dk2mg5s0fs73ec4v10
      ✔️  You are now logged in
      {
        "id": "d4dk2mg5s0fs73ec4v10",
        "kind": "CentralRequest",
        "href": "/api/rhacs/v1/centrals/d4dk2mg5s0fs73ec4v10",
        "status": "failed",
        "cloud_provider": "aws",
        "multi_az": true,
        "region": "us-east-1",
        "owner": "service-account-bf5b2c34-3314-4778-874f-0f6719e3937f",
        "name": "probe-54d885d45b-hhtzv-2465",
        "host": "acs-d4dk2mg5s0fs73ec4v10.acs-stage.rhcloud.com",
        "created_at": "2025-11-17T15:38:03.00888Z",
        "updated_at": "2025-11-17T16:39:25.912079Z",
        "failed_reason": "Creation time went over the timeout. Interrupting central initialization.",
        "instance_type": "standard",
        "cluster_id": "2jttjr1htmkbe3sora28m2ajiorpqc0a"
      }
      

      However, the tenant is present in ArgoCD, even though its synchronization has failed (see screenshots). Need to ensure that the tenant resources chart as well as the associated cloud resources are removed when the provisioning fails with (or without) timeout.

        1. screenshot-1.png
          173 kB
          Yury Kovalev
        2. image-2025-11-18-16-14-46-690.png
          107 kB
          Yury Kovalev

              Unassigned Unassigned
              ykovalev@redhat.com Yury Kovalev
              ACS Cloud Service
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: