You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As can be seen, the response has a value from the remote region, but cannot be queried from the global region.
One possible solution is to honor the remote region id, but, under the covers, make the request down to the remote region, and return task result. We may have to manipulate the href hostnames to present the global region instead of the remote region.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not been updated for at least 3 months.
If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.
Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.
When a user makes a power operations request to a global API, then response value has a task id in the remote region. For example,
Request from region 99
Response
As can be seen, the response has a value from the remote region, but cannot be queried from the global region.
One possible solution is to honor the remote region id, but, under the covers, make the request down to the remote region, and return task result. We may have to manipulate the href hostnames to present the global region instead of the remote region.
The text was updated successfully, but these errors were encountered: