Re: [zones-discuss] preferred way to image-update zones
On 12/ 8/09 11:50 AM, xx wrote: when updating from 126 to 128, one zone would attach: init...@dogpatch:~/.VirtualBox/HardDisks$ pfexec zoneadm -z ldap attach -U Log File: /var/tmp/ldap.attach_log.9hay7p Attaching... Global zone version: ent...@0.5.11,5.11-0.128:20091125T051747Z Non-Global zone version: ent...@0.5.11,5.11-0.111:20090514T145840Z Publisher Check: Zone preferred publisher does not contain ent...@0.5.11,5.11-0.128:20091125T051747Z. Publisher Reset: Copying preferred publisher from global zone. Cache: Using /var/pkg/download. Updating non-global zone: (Stage 1). Output follows DOWNLOAD PKGS FILESXFER (MB) Completed 112/112 10121/10121 126.3/126.3 PHASEACTIONS Removal Phase 4727/4727 Install Phase10622/10622 Update Phase 5073/5073 Updating non-global zone: (Stage 2). Output follows No updates necessary for this image. ERROR: Could not update attaching zone init...@dogpatch:~/.VirtualBox/HardDisks$ zoneadm list -v ID NAME STATUS PATH BRANDIP 0 global running/ ipkg shared init...@dogpatch:~/.VirtualBox/HardDisks$ pfexec zoneadm -z ldap attach Log File: /var/tmp/ldap.attach_log.8ea4wq Attaching... Global zone version: ent...@0.5.11,5.11-0.128:20091125T051747Z Non-Global zone version: ent...@0.5.11,5.11-0.128:20091125T051747Z Evaluation: Packages in ldap are in sync with global zone. Attach complete. and one won't attach: init...@dogpatch:~/.VirtualBox/HardDisks$ pfexec zoneadm -z ldapclient attach -U Log File: /var/tmp/ldapclient.attach_log.E6aOvx Attaching... Global zone version: ent...@0.5.11,5.11-0.128:20091125T051747Z Non-Global zone version: ent...@0.5.11,5.11-0.126:20091022T214456Z Qt WARNING: QClipboard: Unknown SelectionClear event received Publisher Check: Zone preferred publisher does not contain ent...@0.5.11,5.11-0.128:20091125T051747Z. Publisher Reset: Copying preferred publisher from global zone. Cache: Using /var/pkg/download. Updating non-global zone: (Stage 1). Output follows Creating Plan ERROR: Could not update attaching zone init...@dogpatch:~/.VirtualBox/HardDisks$ pfexec zoneadm -z ldapclient attach Log File: /var/tmp/ldapclient.attach_log.aeayVx Attaching... Global zone version: ent...@0.5.11,5.11-0.128:20091125T051747Z Non-Global zone version: ent...@0.5.11,5.11-0.126:20091022T214456Z Evaluation: ldapclient is downrev of the global zone. ERROR: Zone is downrev of global zone. Specify -u to update it. how do you go about figuring out why it won't update? i tried both -U and -u. You might be hitting bug 13190 (http://defect.opensolaris.org/bz/show_bug.cgi?id=13190). Try Jerry Jelinek's workaround as described in the bug report. (NOTE: The attach script that he mentions is /usr/lib/brand/ipkg/attach) Make sure that the publishers used by your zones exist and can be reached from the global zone. Hope that helps, Jordan ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] preferred way to image-update zones
when updating from 126 to 128, one zone would attach: init...@dogpatch:~/.VirtualBox/HardDisks$ pfexec zoneadm -z ldap attach -U Log File: /var/tmp/ldap.attach_log.9hay7p Attaching... Global zone version: ent...@0.5.11,5.11-0.128:20091125T051747Z Non-Global zone version: ent...@0.5.11,5.11-0.111:20090514T145840Z Publisher Check: Zone preferred publisher does not contain ent...@0.5.11,5.11-0.128:20091125T051747Z. Publisher Reset: Copying preferred publisher from global zone. Cache: Using /var/pkg/download. Updating non-global zone: (Stage 1). Output follows DOWNLOAD PKGS FILESXFER (MB) Completed 112/112 10121/10121 126.3/126.3 PHASEACTIONS Removal Phase 4727/4727 Install Phase10622/10622 Update Phase 5073/5073 Updating non-global zone: (Stage 2). Output follows No updates necessary for this image. ERROR: Could not update attaching zone init...@dogpatch:~/.VirtualBox/HardDisks$ zoneadm list -v ID NAME STATUS PATH BRANDIP 0 global running/ ipkg shared init...@dogpatch:~/.VirtualBox/HardDisks$ pfexec zoneadm -z ldap attach Log File: /var/tmp/ldap.attach_log.8ea4wq Attaching... Global zone version: ent...@0.5.11,5.11-0.128:20091125T051747Z Non-Global zone version: ent...@0.5.11,5.11-0.128:20091125T051747Z Evaluation: Packages in ldap are in sync with global zone. Attach complete. and one won't attach: init...@dogpatch:~/.VirtualBox/HardDisks$ pfexec zoneadm -z ldapclient attach -U Log File: /var/tmp/ldapclient.attach_log.E6aOvx Attaching... Global zone version: ent...@0.5.11,5.11-0.128:20091125T051747Z Non-Global zone version: ent...@0.5.11,5.11-0.126:20091022T214456Z Qt WARNING: QClipboard: Unknown SelectionClear event received Publisher Check: Zone preferred publisher does not contain ent...@0.5.11,5.11-0.128:20091125T051747Z. Publisher Reset: Copying preferred publisher from global zone. Cache: Using /var/pkg/download. Updating non-global zone: (Stage 1). Output follows Creating Plan ERROR: Could not update attaching zone init...@dogpatch:~/.VirtualBox/HardDisks$ pfexec zoneadm -z ldapclient attach Log File: /var/tmp/ldapclient.attach_log.aeayVx Attaching... Global zone version: ent...@0.5.11,5.11-0.128:20091125T051747Z Non-Global zone version: ent...@0.5.11,5.11-0.126:20091022T214456Z Evaluation: ldapclient is downrev of the global zone. ERROR: Zone is downrev of global zone. Specify -u to update it. how do you go about figuring out why it won't update? i tried both -U and -u. -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] preferred way to image-update zones
Le 6 déc. 2009 à 03:21, Anil a écrit : It seems to be -U, looking at the source at least: http://cvs.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/cmd/zoneadm/zoneadm.c#attach_func -U seems to be a special (undocumented) update option. Take a look to the comment : === Undocumented 'force update' option for p2v update on attach when zone is in the incomplete state. Change the option back to 'u' and set forced_update flag. === The documented option is '-u' and was also backported to S10 like that. Nico ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] preferred way to image-update zones
Jordan Vaughan skrev: On 12/ 4/09 02:28 PM, Anil wrote: Once a the global zone is upgraded (and rebooted with the new BE), what is the best way to update the zones? It seems like all I would need to do is: pkg -R zone path/root image-update reboot zone This seems like a hack, how would post package processing happen if this is not done from the zone itself? Should I instead *from the zone* take a clone, update parentbe zfs option, set it to active. Then, imate-update the snapshot/clone? This seems like a hack too! Try detaching and attaching the zones that need to be upgraded: # zoneadm -z zone detach [image-update the global zone] [reboot the machine to the new BE] # zoneadm -z zone attach -U You might be able to perform the detach/attach operations while in the updated global zone BE. Please see the Zones FAQ (http://hub.opensolaris.org/bin/view/Community+Group+zones/faq) for details. Hope that helps, Jordan What is the reason for the detach/attach? I have just switched to OS, and when I upgraded from 127 to 128a, with one zone (named swan), I ran (in the global zone): --- pkg image-update --be-name os-snv_128a beadm mount os-snv_128a /a pkg -R /a/zones/swan/root image-update beadm umount os-snv_128a beadm activate os-snv_128a init 6 --- This allows me to update everything without having to stop anything, A speed optimization might be: --- beadm create os-snv_128a beadm mount os-snv_128a /a pkg -R /a image-update pkg -R /a/zones/swan/root image-update beadm umount os-snv_128a beadm activate os-snv_128a init 6 --- Here the image-updates:s can be run in parallel. As I'm a newcomer to opensolaris updates I might be way off. Thomas ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] preferred way to image-update zones
It seems to be -U, looking at the source at least: http://cvs.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/cmd/zoneadm/zoneadm.c#attach_func -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] preferred way to image-update zones
On 12/ 4/09 02:28 PM, Anil wrote: Once a the global zone is upgraded (and rebooted with the new BE), what is the best way to update the zones? It seems like all I would need to do is: pkg -R zone path/root image-update reboot zone This seems like a hack, how would post package processing happen if this is not done from the zone itself? Should I instead *from the zone* take a clone, update parentbe zfs option, set it to active. Then, imate-update the snapshot/clone? This seems like a hack too! Try detaching and attaching the zones that need to be upgraded: # zoneadm -z zone detach [image-update the global zone] [reboot the machine to the new BE] # zoneadm -z zone attach -U You might be able to perform the detach/attach operations while in the updated global zone BE. Please see the Zones FAQ (http://hub.opensolaris.org/bin/view/Community+Group+zones/faq) for details. Hope that helps, Jordan ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] preferred way to image-update zones
Ah, thanks. I knew that was available on Solaris but not in OpenSolaris. The man page had no reference to the -u option (I take it you meant -u and not -U). I will try that out later. -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] preferred way to image-update zones
On 12/ 4/09 03:02 PM, Anil wrote: Ah, thanks. I knew that was available on Solaris but not in OpenSolaris. The man page had no reference to the -u option (I take it you meant -u and not -U). I will try that out later. It probably is -u but I used -U and it worked fine. Go with -u just to be safe. Jordan ___ zones-discuss mailing list zones-discuss@opensolaris.org
