Azure Discovery creating multiple or same CI with same IPs in VM instance class
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello All,
Need help to understand Azure Discovery issue, i.e.
Azure Discovery creating multiple or same CI with same IPs in VM instance class
as of now cmdb_ci_vm_instance Operational Status for all CI's is blank which it should not be
and only install status in use.
What is expected behavior while creating or updating Virtual Machine Instance
in cmdb_ci_vm_instance Class
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Another reason identified, Actual Azure VM are only 300 but lots of new random VM instance are getting created because of Databriks VM instances being deployed must frequently and destroyed as well.
Ideally these should have been handled like normal VM instances as well, I have seen in some account,
these Azure Virtual machine Instances (not databriks vms ) acting normally OOTB setup. e.g. if Terminated Install Status and Operational Status is being marked as retired.
Question is : OOTB Azure VM Instances not updating on the basis of State Attribute value or if old object id is not found in next discovery it should mark as Retired.
Azure VM deletion strategy says install status will be marked as Retired if State is Terminated at least that should work.