- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
â12-15-2023 05:59 AM
Hi All,
We are using Google Cloud Discovery in our environment and observed that Google Cloud Platform (GCP) - Virtual Server pattern is failing due to some Discovery Error. Vms are not getting updated/created for the past 3 months. When checked in the VM schedule, its getting cancelled with the log "Discovery Log is Empty" Please help. Below is the Identification error we are receiving.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
â02-13-2024 11:20 AM
Hi,
Which Servicenow version are you on? Our issue was resolved by upgrading the Servicenow instance to Vancouver and upgrading the Discovery and Service Mapping patterns to the latest version as well. You can try in your sub prod instances and see if it fixes the problem. Hope this helps
Thanks,
Anamika
Anamika

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
â12-16-2023 02:35 AM
Hi
When u say Virtual Machines - Its the OS Based Host/Servers not the VM Instances?
VM Instances- Cloud Discovery Brings it
VM /Hosts- Horizontal/IP based discovery brings it.
Regards
RP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
â12-17-2023 11:26 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
â12-18-2023 07:15 AM
HI ,
Might be some duplicate CI and relationship are there, please cross check and delete the same and try once again using the GCP cloud discovery.
Thanks
Ajay
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
â02-13-2024 11:20 AM
Hi,
Which Servicenow version are you on? Our issue was resolved by upgrading the Servicenow instance to Vancouver and upgrading the Discovery and Service Mapping patterns to the latest version as well. You can try in your sub prod instances and see if it fixes the problem. Hope this helps
Thanks,
Anamika
Anamika