error: Match step predicate is not matched
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-19-2022 03:03 PM
Hi ,
1.Im creating a cloud discovery schedule
2. Im getting a below error when i try to test the account
"Identification sections in pattern failed: section: GCP Service Account Identification, error: Match step predicate is not matched."
I gave valid GCP credential ,have gave correct project id, secret key and email but still getting this error. could anyone can guide me what im missing ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-27-2022 05:31 AM
Hi
I meant that either of this step only succeeds based on what was added as service account.
As you mentioned that it is a GCP project the step "Check if it's a Folder is bound to fail". Can you share screenshot for the error message in the step "Get GCP Accounts" to suggest further steps. In the screenshots you attached it's not there for this specific step.
Also make sure you have configured credential in the service account form and make sure the mid you used to discover GCP schedule has the cloud capabilities.
Please mark Helpful / Accept Solution so that it helps others with similar questions.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-05-2022 09:54 AM
Hi SiD,
Good day!
Please find the attached screenshots for the MID server capabilities and discovery manager setup.
Does the MID server set up should be inside the google cloud environment?
Thanks in advance!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-01-2022 06:05 AM
Hi
MID need not be inside google cloud env.
Are the errors still exist?
If Yes, can you share screenshot of the disco log with exact pattern step "Get GCP Accounts"?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-01-2022 08:27 AM
Hi SiD,
Good day!
Unfortunately, still getting the error. I can't run a discovery now since we have an ongoing HI ticket and the SNOw developers are researching for the solutions. All our cloud discovery are affected as of the moment.
I'll post updates here once they have a solution.
Thank you for your response!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-23-2022 08:30 AM
Hi Ceasar ,
I have followed this article
https://hiwave.servicenowservices.com/kb?id=kb_article_view&sysparm_article=KB0784531
to enable Cloud resource manager api
then i can able to successfully discover
