Ops Center 12c: Added then deleted a Non-global Zone but it is still Being Probed By Ops Center
(Doc ID 1529704.1)
Last updated on FEBRUARY 11, 2019
Applies to:
Enterprise Manager Ops Center - Version 12C to 12c (12.1) [Release 12.0]Information in this document applies to any platform.
Symptoms
A non-global zone was built on our Enterprise Controller as a test. It was automatically detected and added into Ops Center because the global zone monitors itself. The zone was later deleted. 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 <ZONE>
/usr/sbin/zoneadm -z <ZONE> install
/usr/sbin/zlogin -C <ZONE>
/usr/sbin/zoneadm -z <ZONE> boot
/usr/sbin/zoneadm -z <ZONE> halt
/usr/sbin/zoneadm -z <ZONE> uninstall
/usr/sbin/zonecfg -z <ZONE> delete
While parsing the oem-ec logs/cacao logs looking for another bug, it was discovered that the EC was still probing the deleted zone!
There were no entries in /etc/zones/index and no /etc/zones/<ZONE>.xml files. The Enterprise Controller did not show an asset for the zone.
Why is Ops Center still probing for it?
Changes
The global zone was already monitored by Ops Center. A local zone was added to the global zone, and then deleted shortly after this.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |