The following table describes what will happen when packaging commands are used on a system with non-global zones in various states.
A non-global zone transitions to the unavailable state when the storage for the zone is not accessible or when the image of the zone, which is described in pkg(5), is out of sync with the global zone's image. This state transition occurs to prevent a problem that is affecting a non-global zone from blocking package operations in the global zone.
When a zone's storage is temporarily unavailable and package operations that change the version of installed software occur, it is likely that after fixing the storage problem, the zone might need to be attached by using one of the solaris brand's attach options that allow for updates. For example, zoneadm –z zonename attach –u might be required to synchronize versions of critical software between the global zone and a non-global zone that is in the unavailable state.