My Oracle Support Banner

Solaris Cluster 4.x unintended boot environment created at zone failover, ghost BE boot environment phenomena (Doc ID 2046143.1)

Last updated on AUGUST 14, 2020

Applies to:

Solaris Cluster - Version 4.2 to 4.2 [Release 4.2]
Information in this document applies to any platform.

Symptoms

When a zone on a Solaris Cluster  is failed over and the zone is booted to a new BE boot environment you may see that an additional backup boot environment was created. In addition if there is no boot environment of global zone is associated with zone's BE it is essentially an orphan boot environment as it can no longer be updated or changed and it is not automatically deleted either.  Before Solaris 11.3 these BEs may not be easy to recognize.

 



Changes

 Solaris 11.3 has been incorporated code change to better handle orphan zone boot environments and Oracle Solaris Cluster 4.3 is using those enhancements.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.