This article describes one of the use cases resulting in the error - "Could not redirect to the Discovery Status" when the "Discover now" UI action is clicked under the "Related Links" section in the Discovery Schedule page.

Before Paris, If a user has master + member account(s) in the instance and if any new member account is added via the cloud console then the user has to edit the Cloud Schedule in the instance and refresh the member accounts manually every time by clicking the "Refresh" button available below the slush bucket present in the Account Validation screen of Cloud Wizard, a custom UI to create the Cloud Discovery schedule.

In Paris, a feature (enhancement) is introduced to refresh the member account(s) of the master account and the respective datacenter(s) as well for each account automatically, tracked via their own discovery statuses, before the start of the Cloud Discovery run. Please note, only the discovery schedule(s) of type - "Cloud Resources" are affected due to this feature.

This feature is controlled via the system property - "glide.discovery.cdu.auto_refresh_sub_accounts_and_ldcs" and value is a boolean. Out of the box, the property value is FALSE and it indicates that the auto-refresh of sub-account(s) and LDC(s) (Datacenter(s)) is disabled. To enable it, the value can be changed to TRUE.

Problem

If the system property is set to TRUE and on clicking the “Discover Now” UI action in the Cloud Discovery Schedule then the refresh of member(s) and the datacenter(s) is triggered and then the actual cloud discovery schedule starts.

Due to the above behavior, it takes some time to complete the whole refresh thing and actual discovery run to start so there will be a time delay for redirecting to the Discovery Status (newly created one when clicking Discover Now UI Action) thus resulting in the error – “Could not redirect to the Discovery Status” because the API calls for refreshing Members and Datacenters may be in progress or near completion.

Workaround

Set the property value to FALSE.

Other issues that result in the error - “Could not redirect to the Discovery Status”