Environment
- Yugabyte Anywhere: YugabyteDB Anywhere (YBA) v2024.x and later
Issue
When attempting to edit a Cloud Provider in YugabyteDB Anywhere (YBA), for example to enable "Use IAM Role" or update credentials, the operation fails with the following error message in the UI or logs:
Edit provider request failed: Provider <UUID> resources are currently in use
This prevents the user from saving changes to the provider configuration.
Cause
This error occurs because YugabyteDB Anywhere (YBA) enforces a lock on Cloud Provider configurations while there are active tasks running that utilize resources managed by that provider. The error indicates that one or more of these tasks are currently in progress. The resolution is to identify the running task and wait for it to complete.
Common tasks that can trigger this lock include:
- Backups (Scheduled or Manual)
- Universe Creation or Editing
- Node Scaling (Adding/Removing nodes)
- Software Upgrades
- Maintenance tasks
Resolution
To resolve this issue, follow these steps to identify and wait for the conflicting tasks.
Identify Active Tasks: Go to the Tasks tab in YBA and filter by Running. Look for any tasks (like Backups or Universe Edits) linked to the Cloud Provider you are trying to modify.
Wait for Completion: Allow these tasks to finish successfully. If a task stalls indefinitely, investigate with the help of Yugabyte Support by raising a support case or abort it.
Retry the Edit: Once active tasks clear, return to Configs > Cloud Providers, apply your changes, and save.
Additional Information
If no tasks are running and you still encounter issues editing the provider (specifically if the error indicates the provider is "in use" by Universes rather than "resources currently in use"), you may be encountering a restriction on editing providers with active deployments. In that case, refer to the KB article Editing an In-Use Cloud Provider in YBA (YugabyteDB Anywhere) or contact Support.
Reference ID: SUPPORT-849
Comments
0 comments
Article is closed for comments.