jfyi, if you do 'pkg image-upgrade' from build (132) to build 133 and you do 
have  
non-global zones in the installed state, you may run into:

Bug 14668 - pkg directory action does work when there is none
http://defect.opensolaris.org/bz/show_bug.cgi?id=14668

note that you should only hit this if you have installed SUNWscp.

see bugs:
     Bug 14667 - compatibility/ucb delivers /export and /home
     http://defect.opensolaris.org/bz/show_bug.cgi?id=14667
and
     
     http://bugs.opensolaris.org/view_bug.do?bug_id=6928051

workaround_1:
- uninstall the zones before image-upgrade

workaround_2 (as reported in the bug):
- rebooting into single user, entering "maintenance
  mode" as "root" and image-updating from there. 

---------------------------------------------------------

NB: _strongly discouraged_:

workaround_3: 
- detach all of the zones on the system before the image-update.
 
Why is workaround_3 strongly discouraged ?

this is strongly discouraged as no new BE gets created for the installed Zone,
instead the current Zone BE is updated if you do an attach -u following this
image-update.
 
if you want to switch back to a previous build BE later, eg. 132 (because 
there's
something in 133 that prevents you from doing what you want), the Zones BE
will no longer match the global BE, eg. GZ BE will be build 132 but the
NGZ BE will still be 133.

Net result, Zone not usable anymore in previous BE with build 132, ie.
you can not downgrade the NGZ BE again.

---
frankB
_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org

Reply via email to