Re: [zones-discuss] Does update on attach add information from the new systems kernel patch ?
Geoff Shipman wrote: Jerry, I received update they did not use a force option to the attach just the -u. They noted that no log file was created in the /var/sadm/system/logs directory of the NGZ. This attach was stymied originally by a Veritas package VRTSat that had patch 117499-02 with garbage characters in the obsoletes field of the pkginfo file. Once they followed Symantecs instructions on removal of the patch and access a clean version from the Symantec ftp site the attach went OK, allowing the zoneadm attach to recreate the SUNWdetach information. The NGZ still shows garbage in the pkginfo information for VRTSat from the showrev -p data and the kernel patch 13-01 is not listed in the showrev output. I asked them to detach the NGZ and run the attach -u again after removing the SUNWdetach.xml to see if this time they get a log file created. Just about the first thing that the update on attach does is create the log file, so if there isn't one, then I'm not really sure what they did or how the zone could have ended up in the installed state. Clearly something went wrong here so its hard to draw any conclusions about the state of the pkg metadata at this point. If this is reproducible, then we can dig into it further. It sounds like the pkg metadata is still corrupted in the NGZ due to the bad pkg? Cleaning that up might help things, but it would be nice to see whats really going on during the whole process. Jerry ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Does update on attach add information from the new systems kernel patch ?
Geoff and Jerry, On Feb 4, 2009, at 2:17 AM, Geoff Shipman wrote: Jerry, I received update they did not use a force option to the attach just the -u. They noted that no log file was created in the /var/sadm/system/logs directory of the NGZ. This attach was stymied originally by a Veritas package VRTSat that had patch 117499-02 with garbage characters in the obsoletes field of the pkginfo file. Once they followed Symantecs instructions on removal of the patch and access a clean version from the Symantec ftp site the attach went OK, allowing the zoneadm attach to recreate the SUNWdetach information. The NGZ still shows garbage in the pkginfo information for VRTSat from the showrev -p data and the kernel patch 13-01 is not listed in the showrev output. We have had some issues with the damaged VRTSat package, the fixed version of the same version of the patch together with the instructions did not solve the whole problem for us when using it with zones. If I remember correctly this fix did in fact damage the package database, or at least make it inconsistent with the files present on the system. The solution was to remove the whole VRTSat package, reapply the package and then apply the working version on the patch version directly without applying the damaged version first. The pkgadd procedure would complain regarding already present or missing files but after this we ended up with a consistent package database again. It's late here in Sweden but i can give you the exact information on what I experienced and how it was solved tomorrow morning if it's of any interest. Regards Henrik Johansson http://sparcv9.blogspot.com ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Does update on attach add information from the new systems kernel patch ?
Geoff Shipman wrote: Hello All, I attached a NGZ that was from an alternate system to a Update 6 system using the -u option. The NGZ is sparse but I don't think a whole root would behave much differently. The update worked and the NGZ was attached but I noted that the kernel revision via uname -a was the new version but a showrev -p for that patch ID does not show the patch installed. The global side does show the kernel patch as installed. Is this expected behavior ?. I noted that the /etc/release was not updated reflecting the new kernel environment the NGZ was running under. This lack of update to /etc/release though is not expected as only an upgrade or fresh install modifies that entry. This is: 6715679 update on attach should update etc/release file which is fixed in S10u7. Jerry ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Does update on attach add information from the new systems kernel patch ?
Jerry, Thanks for the update on the /etc/release file. The customer is more concerned regarding the kernel patch info not listed in the NGZ. From uname output in the NGZ we can see the kernel matches the global value. Its the lack of showrev -p data for that kernel revision that customer is concerned with. Thanks Geoff From Global zone. # uname -a SunOS plnvssun1sbo12 5.10 Generic_13-01 sun4v sparc SUNW,Sun-Fire-T200 plnvssun1sbo12# showrev -p|grep 13-01 Patch: 13-01 Obsoletes: 126264-01, 128340-01, 137106-01, 137278-01, 138106-02, 138114-01, 138850-01 Requires: 118833-36, 120011-14, 127127-11, 137137-09 Incompatibles: Packages: SUNWcsu, SUNWcsl, SUNWckr, SUNWcakr, SUNWmdb, SUNWhea, SUNWcslr, SUNWust1 From newly update attached NGZ. # zlogin spslogger01 [Connected to zone 'spslogger01' pts/2] Last login: Thu Jan 29 11:06:17 on pts/2 spslogger01# uname -a SunOS spslogger01 5.10 Generic_13-01 sun4v sparc SUNW,Sun-Fire-T200 spslogger01# showrev -p|grep 13-01 On Mon, 2009-02-02 at 07:40, Jerry Jelinek wrote: Geoff Shipman wrote: Hello All, I attached a NGZ that was from an alternate system to a Update 6 system using the -u option. The NGZ is sparse but I don't think a whole root would behave much differently. The update worked and the NGZ was attached but I noted that the kernel revision via uname -a was the new version but a showrev -p for that patch ID does not show the patch installed. The global side does show the kernel patch as installed. Is this expected behavior ?. I noted that the /etc/release was not updated reflecting the new kernel environment the NGZ was running under. This lack of update to /etc/release though is not expected as only an upgrade or fresh install modifies that entry. This is: 6715679 update on attach should update etc/release file which is fixed in S10u7. Jerry -- Geoff Shipman - (303) 272-9955 Systems Technology Service Center - Operating System Solaris and Network Technology Domain Americas Systems Technology Service Center ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Does update on attach add information from the new systems kernel patch ?
Geoff Shipman wrote: Jerry, Thanks for the update on the /etc/release file. The customer is more concerned regarding the kernel patch info not listed in the NGZ. From uname output in the NGZ we can see the kernel matches the global value. Its the lack of showrev -p data for that kernel revision that customer is concerned with. Can you send me the log from the zone update. Thanks, Jerry ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Does update on attach add information from the new systems kernel patch ?
Jerry and Mike, I have requested the log data as well as verification the -F option was not used. I also asked for showrev -p output from the NGZ. I will update when available. The log data looks to be in the /var/sadm/system/logs directory of the NGZ and the file is called update_log. Thanks Geoff On Mon, 2009-02-02 at 08:25, Jerry Jelinek wrote: Geoff Shipman wrote: Jerry, Thanks for the update on the /etc/release file. The customer is more concerned regarding the kernel patch info not listed in the NGZ. From uname output in the NGZ we can see the kernel matches the global value. Its the lack of showrev -p data for that kernel revision that customer is concerned with. Can you send me the log from the zone update. Thanks, Jerry -- Geoff Shipman - (303) 272-9955 Systems Technology Service Center - Operating System Solaris and Network Technology Domain Americas Systems Technology Service Center ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Does update on attach add information from the new systems kernel patch ?
On Mon, Feb 2, 2009 at 9:07 AM, Geoff Shipman geoff.ship...@sun.com wrote:
Jerry,
Thanks for the update on the /etc/release file. The customer is more
concerned regarding the kernel patch info not listed in the NGZ.
From uname output in the NGZ we can see the kernel matches the global
value. Its the lack of showrev -p data for that kernel revision that
customer is concerned with.
The apparent inaccuracy of showrev -p scared me a bit, so I took a
look at an Update 4 zone that I attached to an Update 6 machine:
# uname -srv
SunOS 5.10 Generic_137137-09
# cat /etc/release
Solaris 10 8/07 s10s_u4wos_12b SPARC
Copyright 2007 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 16 August 2007
# showrev -p | nawk '$2 == 137137-09 { print $1, $2 }'
Patch: 137137-09
That all looks OK (aside from the debatable /etc/release - it is
update not upgrade...).
Are you sure that the zone you are dealing with was attached properly?
Was it maybe attached with -F (force, ignoring broken stuff) rather
than -u (update on attach)?
--
Mike Gerdts
http://mgerdts.blogspot.com/
___
zones-discuss mailing list
zones-discuss@opensolaris.org
