Re: [zones-discuss] Zones patching issues using attach -u
On Tue, Sep 15, 2009 at 2:02 PM, Jerry Jelinek wrote: > Gael wrote: >> >> Hello >> >> I have been experimenting a few ways to speed up patching a bunch of >> machines running whole zones (parallel patching, zoneadm attach -u). >> I have encountered one issue with the attach -u way... Before initiating a >> case with sun, I was wondering if it was a well known issue... >> >> The GZ is initially running Solaris 10 U6 with kernel patch 13-08 (and >> other patches from the same period). >> >> I start by applying 119254-70, 119313-28 and 12-05 while the machine >> is >> in multiuser mode, then I shutdown and detach the zones. >> I bring back the machine in single user mode and apply a collection of >> about >> 190 patches (smpatch analyze output from a few days ago) which brings the >> machine at the kernel version 141414-10. >> >> The patching appears to go fine for the GZ >> >> apss8003:/var/sadm/patch #pkginfo -p >> apss8003:/var/sadm/patch # >> >> But when zoneadm attaching -u the zones, pkginfo reports multiple >> partially >> failing packages adds ... >> >> apss8003:/var/sadm/patch #zlogin test pkginfo -p >> system SUNWcsr Core Solaris, (Root) >> system SUNWgssc GSSAPI CONFIG V2 >> system SUNWkrbr Kerberos version 5 support >> (Root) >> system SUNWntpr NTP, (Root) >> system SUNWppror PatchPro core functionality >> (Root) >> system SUNWsacom Solstice Enterprise Agents >> 1.0.3 >> files for root file system >> >> # cat /zones/test/root//var/sadm/system/logs/update_log | egrep >> "partially|corrupt|pathname does not exist|" >> >> = SUNWcsr >> pkgadd: ERROR: source path >> >> >> is corrupt >> pathname does not exist >> Installation of on zone partially failed. >> >> = SUNWgssc >> pkgadd: ERROR: source path >> >> >> is corrupt >> pathname does not exist >> Installation of on zone partially failed. >> >> = SUNWkrbr >> pkgadd: ERROR: source path >> >> >> is corrupt >> pathname does not exist >> Installation of on zone partially failed. >> >> = SUNWntpr >> pkgadd: ERROR: source path >> >> >> is corrupt >> pathname does not exist >> Installation of on zone partially failed. >> >> = SUNWppror >> pkgadd: ERROR: source path >> >> >> is corrupt >> pathname does not exist >> Installation of on zone partially failed >> >> = SUNWsacom >> pkgadd: ERROR: source path >> >> >> is corrupt >> pathname does not exist >> Installation of on zone partially failed. >> >> If creating a new zone after the patching, there is no partial packages in >> that newly build zone. >> >> The patch list being a little bit lengthy, I can send it privately when >> asked... > > This is bug: > > 6857294 zoneadm attach leads to partially installed packages > > I believe a T patch might be available for the S10 SVr4 packaging code > if you need it, but I see that the fix has not yet been integrated > into the nv SVr4 packaging code. It is scheduled for b124. > > Jerry I stumbled across this a while back with SUNWservicetagr. My workaround was: d=/var/sadm/pkg/SUNWservicetagr/save/pspool/SUNWservicetagr/reloc/var/svc/manifest/network mkdir -p $d cp /var/svc/manifest/network/st*.xml $d In the last week or so the CR (6833642) logged due to the case that I opened related to this was changed to "cause known" and is now "related to" 6857294. -- Mike Gerdts http://mgerdts.blogspot.com/ ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Zones patching issues using attach -u
Gael wrote: Hello I have been experimenting a few ways to speed up patching a bunch of machines running whole zones (parallel patching, zoneadm attach -u). I have encountered one issue with the attach -u way... Before initiating a case with sun, I was wondering if it was a well known issue... The GZ is initially running Solaris 10 U6 with kernel patch 13-08 (and other patches from the same period). I start by applying 119254-70, 119313-28 and 12-05 while the machine is in multiuser mode, then I shutdown and detach the zones. I bring back the machine in single user mode and apply a collection of about 190 patches (smpatch analyze output from a few days ago) which brings the machine at the kernel version 141414-10. The patching appears to go fine for the GZ apss8003:/var/sadm/patch #pkginfo -p apss8003:/var/sadm/patch # But when zoneadm attaching -u the zones, pkginfo reports multiple partially failing packages adds ... apss8003:/var/sadm/patch #zlogin test pkginfo -p system SUNWcsr Core Solaris, (Root) system SUNWgsscGSSAPI CONFIG V2 system SUNWkrbrKerberos version 5 support (Root) system SUNWntprNTP, (Root) system SUNWppror PatchPro core functionality (Root) system SUNWsacom Solstice Enterprise Agents 1.0.3 files for root file system # cat /zones/test/root//var/sadm/system/logs/update_log | egrep "partially|corrupt|pathname does not exist|" = SUNWcsr pkgadd: ERROR: source path is corrupt pathname does not exist Installation of on zone partially failed. = SUNWgssc pkgadd: ERROR: source path is corrupt pathname does not exist Installation of on zone partially failed. = SUNWkrbr pkgadd: ERROR: source path is corrupt pathname does not exist Installation of on zone partially failed. = SUNWntpr pkgadd: ERROR: source path is corrupt pathname does not exist Installation of on zone partially failed. = SUNWppror pkgadd: ERROR: source path is corrupt pathname does not exist Installation of on zone partially failed = SUNWsacom pkgadd: ERROR: source path is corrupt pathname does not exist Installation of on zone partially failed. If creating a new zone after the patching, there is no partial packages in that newly build zone. The patch list being a little bit lengthy, I can send it privately when asked... This is bug: 6857294 zoneadm attach leads to partially installed packages I believe a T patch might be available for the S10 SVr4 packaging code if you need it, but I see that the fix has not yet been integrated into the nv SVr4 packaging code. It is scheduled for b124. Jerry ___ zones-discuss mailing list zones-discuss@opensolaris.org
[zones-discuss] Zones patching issues using attach -u
Hello I have been experimenting a few ways to speed up patching a bunch of machines running whole zones (parallel patching, zoneadm attach -u). I have encountered one issue with the attach -u way... Before initiating a case with sun, I was wondering if it was a well known issue... The GZ is initially running Solaris 10 U6 with kernel patch 13-08 (and other patches from the same period). I start by applying 119254-70, 119313-28 and 12-05 while the machine is in multiuser mode, then I shutdown and detach the zones. I bring back the machine in single user mode and apply a collection of about 190 patches (smpatch analyze output from a few days ago) which brings the machine at the kernel version 141414-10. The patching appears to go fine for the GZ apss8003:/var/sadm/patch #pkginfo -p apss8003:/var/sadm/patch # But when zoneadm attaching -u the zones, pkginfo reports multiple partially failing packages adds ... apss8003:/var/sadm/patch #zlogin test pkginfo -p system SUNWcsr Core Solaris, (Root) system SUNWgsscGSSAPI CONFIG V2 system SUNWkrbrKerberos version 5 support (Root) system SUNWntprNTP, (Root) system SUNWppror PatchPro core functionality (Root) system SUNWsacom Solstice Enterprise Agents 1.0.3 files for root file system # cat /zones/test/root//var/sadm/system/logs/update_log | egrep "partially|corrupt|pathname does not exist|" = SUNWcsr pkgadd: ERROR: source path is corrupt pathname does not exist Installation of on zone partially failed. = SUNWgssc pkgadd: ERROR: source path is corrupt pathname does not exist Installation of on zone partially failed. = SUNWkrbr pkgadd: ERROR: source path is corrupt pathname does not exist Installation of on zone partially failed. = SUNWntpr pkgadd: ERROR: source path is corrupt pathname does not exist Installation of on zone partially failed. = SUNWppror pkgadd: ERROR: source path is corrupt pathname does not exist Installation of on zone partially failed = SUNWsacom pkgadd: ERROR: source path is corrupt pathname does not exist Installation of on zone partially failed. If creating a new zone after the patching, there is no partial packages in that newly build zone. The patch list being a little bit lengthy, I can send it privately when asked... Regards -- Gael Martinez ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] s10 brand Phase I webrev
Peter Memishian wrote: > We've completed the development for the Phase I > work on the solaris10 brand. I've posted a > full webrev at: > > http://cr.opensolaris.org/~gjelinek/webrev.646/ > > Let me know if there are any comments. I see that ip-type=exclusive is regarded as "experimental" in s10_support.c; is that planned for Phase II? Yes, that's right. We haven't done any of the testing or evaluation yet on what it will take to make exclusive fully work for the brand but we will do that for Phase II. Thanks, Jerry ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] s10 brand Phase I webrev
> We've completed the development for the Phase I > work on the solaris10 brand. I've posted a > full webrev at: > > http://cr.opensolaris.org/~gjelinek/webrev.646/ > > Let me know if there are any comments. I see that ip-type=exclusive is regarded as "experimental" in s10_support.c; is that planned for Phase II? -- meem ___ zones-discuss mailing list zones-discuss@opensolaris.org
[zones-discuss] s10 brand Phase I webrev
We've completed the development for the Phase I work on the solaris10 brand. I've posted a full webrev at: http://cr.opensolaris.org/~gjelinek/webrev.646/ Let me know if there are any comments. Thanks, Jerry ___ zones-discuss mailing list zones-discuss@opensolaris.org
