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-20-2022 12:56 AM
Hi
You need to open the discovery status table and see the respective status log that corresponds to service account validation and debug pattern log to see why that step fails.
Only after which we can get to know how to proceed further. Kindly check and if you don't understand share the screenshot if possible.
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
‎06-21-2022 11:54 AM
So, we have a similar dilemma here. We're getting the same issue when setting up the GCP discovery. We successfully discovered AWS and AZURE resources by the way without pains.
Only GCP is more complicated than of other cloud platform.
I check the patterns and I got this. See Attached snapshots.
Our GCP admin mentioned that the Project ID is not a folder, but the pattern always checks "https://cloudresourcemanager.googleapis.com/v2/folders/Project ID"
During the test, it has queried compute engine api (VMs) 99 times, 100% success
During Creation of discovery it says "Account Validation is successful", but in the Discovery Log it failed on the pattern. See attachments.
Hopefully someone can shed light on this issues. Thank you in advance!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-23-2022 06:14 AM
Hi
I saw the attachments and it looks to be a configuration issue at your end on the Service account vs mid vs cred mapping.
Usually you can add a project or a folder under GCP as a Service Account in SNOW. The validation pattern checks if it's a folder or project and validates at the end.
So only either of your steps "Check if it's a Folder" or "Get GCP Accounts" only will succeed based on what you added [folder/project] as a Service Account.
But in this case this is a SNOW error about credentials, so either the cred field is not populated at all OR the cred would have been mapped only to a specific MID and the service account wouldn't be linked to that cred. This kind of misconfiguration might lead to this error.
Please check the configuration at your end.
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
‎06-23-2022 10:07 AM
Hi SiD,
Good day!
Thanks for your response, I confirmed from the GCP admin that the GCP Service Account we're using is a GCP Project.
"So only either of your steps "Check if it's a Folder" or "Get GCP Accounts" only will succeed based on what you added [folder/project] as a Service Account." for this, do we need to update the pattern to Get GCP instead of Check if it's a Folder?
Thanks,
Ceasar