Ops Center 12c: Added then deleted a Non-global Zone but it is still Being Probed By Ops Center
Last updated on OCTOBER 14, 2016
Applies to:Enterprise Manager Ops Center - Version 12C to 12C [Release 12.0]
Information in this document applies to any platform.
I built a non-global zone on the EC server called 'edzone' which was automatically detected and added into Ops Center because the globalzone was already monitoring said globalzone, later I deleted the zone. The zone deletion removed all zone-related file systems for the zone. The EC removed it from the asset tab.
Add and delete steps were:
/usr/sbin/zonecfg -z edzone
/usr/sbin/zoneadm -z edzone install
/usr/sbin/zlogin -C edzone
/usr/sbin/zoneadm -z edzone boot
/usr/sbin/zoneadm -z edzone halt
/usr/sbin/zoneadm -z edzone uninstall
/usr/sbin/zonecfg -z edzone delete
I was investigating the oem-ec logs/cacao log file for another bug when I discovered that the EC is still probing the non-existant zone!
There are no entries in /etc/zones/index and no /etc/zones/edzone.xml files.
The EC does not even have an asset for 'edzone'
Why is Ops Center still probing for it?
Globalzone was already monitored by Ops Center, we just added and deleted a local zone onto said globalzone.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms