Loading...
Loading...
During Master account creation flow with accessor from CDU UI, on test account credential resolution starts where script include(CloudDiscoveryScheduleConfig) creates the record in “cmdb_ci_cloud_service_account” which triggers BR to issue service_account_reload System command. On record insertion to the table, test credential flow waits for 2 seconds(hard coded value) to make sure credential is synced to mid server. Recent fix for DEF0411667(PRB1674231) introduced debouncing logic for System command “service_account_reload” which is backed by a property to enable the debouncing logic by default . This debouncing logic accumulates redundant service_account_reload System commands for 10 seconds and process the command after that. Meanwhile, test credential flow from step 2 calls the mid to resolve the credential for account which in turn check the above table for accessor account details. But since the debouncing logic waits for 10 seconds before processing, the records are not yet synced to the mid server. This results in failure to resolving credential. Steps to Reproduce 1. Create an accessor account in "cmdb_ci_cloud_service_account" table. 2. Go to Discovery home page -> Add an AWS schedule 3. Add master account and role along with accessor account. Test account validation fails.
WorkAround: 1. Add service account to be discovered in cmdb_ci_service_account with accessor account. 2. Go to CDU UI select 'Select Account'. Run Test Account.
PRB1712052
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.