Uploaded image for project: 'Managed Service - API'
  1. Managed Service - API
  2. MGDAPI-4549

The DnsBypassThree.... alerts can fire for tenants scheduled for deletion

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Critical Critical
    • 1.31.0
    • None
    • None
    • RHOAM Sprint 34, RHOAM Sprint 35, RHOAM Sprint 36, RHOAM Sprint 38

      WHAT
      At the moment the logic randomly selects a system-developer and system-provider tenant route to test for availability.
      If a route selected is related to an account/tenant that is scheduled for deletion, this will result in a 404. See attached.

      HOW
      Add some intelligence to how we select a system-developer and system-provider route.
      At least, ensure that the account is not scheduled for deletion.

      Potentially use porta client and hit api to get accounts in the middle state, "approved" 

      TESTS
      Create an account/tenant and delete it.
      Create a new account
      Ensure alert does not fire.

      DONE
      <bullet point items for what should be completed>

              jfitzpat_rhmi Jim Fitzpatrick (Inactive)
              bgallagh@redhat.com Brian Gallagher
              Tsvetoslav Dimov Tsvetoslav Dimov (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: