On 2/21/10 10:17 AM, Frank Batschulat (Home) wrote:
On Sun, 21 Feb 2010 18:15:32 +0100, Evan Layton<[email protected]> wrote:
On 2/21/10 9:31 AM, Frank Batschulat wrote:
if you are doing an image upgrade from build 132 to build 133 and you do
havenon-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
workaround_1:
- uninstall the zones before image-upgrade
workaround_2 (as reported in the bug):
While this does allow for a successful image-update it does not result
in zones that are usable. In the new global zone BE you will see the
zones and they will report that they are installed however attempting
to boot them will fail:
# zoneadm -z z2 boot
zone 'z2': ERROR: no active dataset.
zone 'z2':
zoneadm: zone 'z2': call to zoneadmd failed
This is because the image-update done in single user mode will not
create the zone datasets for the non-global zones in the new global
zone BE.
If you wish to maintain your zones into the new global zone BE then
workaround_3 is really the only way to do it. Yes this makes it so
your zones are no longer available in the old BE but they are available
within the new global zone BE.
- rebooting into single user, entering "maintenance
mode" as "root" and image-updating from there.
Please note that you should only hit this if you have installed SUNWscp.
see bugs:
http://defect.opensolaris.org/bz/show_bug.cgi?id=14667
and
http://bugs.opensolaris.org/view_bug.do?bug_id=6928051
workaround_3:
- detach all of the zones on the system before the image-update.
NB: this is strongly discouraged as no new BE gets created for the installed
Zone,
instead the current Zone BE is updated.
This is also true for workaround_2. In both cases no new dataset or
BE gets created for the installed zone. However with workaround_3
it is at least possible to do a zoneadm attach -u to make the zone
accessible within the updated BE. Whereas with workaround_2 there
are additional steps needed to make the zones accessible in the
updated BE and the end result can be the same, the zones are not
accessible in the old global zone BE.
-evan
if you want to swicth back to a previous build 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 132, NGZ BE will still be 133.
Zone not usable anymore in previous BE 132.
cheers
frankB
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
