0 Replies Latest reply on Jan 18, 2008 8:11 AM by Stefan Kruth

    Problems with patch dependencies Solaris 10. This could be a SUN bug.

    Stefan Kruth

      I came across the following problem. This is not resolveable via xerf_content.info or other methods except the method from SUn (see below):

       

      Document Audience: SPECTRUM

      Document ID: 6607483

      Title: Unresolvable patch dependency between patch 125547-01/125547-02 and 120011-14

      Copyright Notice: Copyright © 2007 Sun Microsystems, Inc. All Rights Reserved

      Update Date: Wed Sep 26 00:00:00 MDT 2007

       

      Bug ID: 6607483

       

      Synopsis: Unresolvable patch dependency between patch 125547-01/125547-02 and 120011-14

       

      Category: consolidation

       

      Subcategory: os-net-patch

       

      State: 11-Closed

       

      Description:

       

      Attempting to update T2000 running Solaris 10 U3. "smpatch analyze" showing the following:

       

      125547-02 SunOS 5.10: zoneadm indirect dependency patch

      120011-14 SunOS 5.10: kernel patch

      126206-03 SunOS 5.10: zebra ripd patch quagga

      126442-01 SunOS 5.10: ac97.h patch

      126651-01 SunOS 5.10: tar patch

      125378-02 SunOS 5.10: timezones patch

      125174-02 SunOS 5.10: tl driver patch

      126421-01 SunOS 5.10: format patch

      123301-01 SunOS 5.10: i2c_svc patch

      125898-01 SunOS 5.10: locator patch

      125894-01 SunOS 5.10: cut patch

      126432-01 SunOS 5.10: ntwd driver patch

      126258-02 SunOS 5.10: in.ftpd patch

      125167-01 SunOS 5.10: gssd patch

      126647-01 SunOS 5.10: InfiniBand header files patch

      125172-01 SunOS 5.10: llc2 driver patch

      126542-01 SunOS 5.10: snmpdx and mibiisa patch

      123895-03 SunOS 5.9 5.10: Common Agent Container (cacao) monitoring 2.1 upgrade patch 03

      123894-03 SunOS 5.9 5.10: Common Agent Container (cacao) secure web server 2.1 upgrade patch 03

       

      Patch 125547-02 is marked "interactive" so should be installed using patchadd. System shutdown to single user and patch add attempted which gets the following:

       

      -


       

      bash-3.00# patchadd /var/sadm/spool/125547-02

      Validating patches...

       

      Loading patches installed on the system...

       

      Done!

       

      Loading patches requested to install.

       

      Done!

       

      Checking patches that you specified for installation.

       

      Done!

       

       

      Approved patches will be installed in this order:

       

      125547-02

       

       

      Checking installed patches...

      Executing prepatch script...

       

      Patch 122660-10 needs to be installed before this patch can be

      successfully installed on this system.

       

      Please install 122660-10 and then run patchadd again for this patch.

      The prepatch script exited with return code 1.

       

      Patchadd is terminating.

       

      -


       

      So Patch 125547-02 is dependant on 122660-10. According to patch 122660-10 README, it has been obseleted by 120011-14. Have not attempted to install 120011-14 prior to 125547-02 as this "smpatch analyze" output should be considered patchorder list. If 120011-14 can be installed prior to 125547-02, then patchorder output of "smpatch analyze" should be modified to reflect and allow patching to continue.

       

      Date Modified: 2007-09-21 02:11:01 GMT+00:00

       

       

      Ok ... appears to be a true unresolved circular patch dependency issue. Just attempted to load 120011-14 and got the following:

       

      -


      Checking patches that you specified for installation.

       

      Done!

       

       

      The following requested patches will not be installed because

      at least one required patch is not installed on this system.

       

      0 For patch 120011-14, required patch 125547-01 does not exist.

       

       

       

      No patches to install.

      -


       

      So can't install 125547-01 because it doesn't know that 122660-10 was been obsoleted by 120011-14 and Can't install 120011-14 because its dependent on 125547-01.

       

      Date Modified: 2007-09-21 13:17:55 GMT+00:00

       

       

      Work Around:

       

      move prepatch script out of the patch directory

       

      eg.

       

      mv ./125547-02/prepatch .

      patchadd ./125547-02

       

      Date Modified: 2007-09-24 12:32:40 GMT+00:00

       

       

      Hi

      if 122660-09 is installed and a user tries to run patchadd 120011-14 then patchadd will fail due to a bug in zoneadmd ( CR 6523454 ).

       

      So as 120011-14 obsoletes 122660-10 due to how splitgate works we also need to ensure that 122660-10 is installed, as otherwise patchadd will fail.

       

      So we created patch 125547 that by way of a prepatch enforces that 122660-10 is installed. We could not have 125547 HARD REQUIRE 122660-10 as that would lead to a dependency on 120011-14 itself, which is what we are trying to avoid to start with.

       

       

      Enda

       

      Date Modified: 2007-09-24 13:10:59 GMT+00:00

       

       

      to summarise :

       

      prepatch should not be tampered with as it is there to enforces an explicit requirement

       

      simply follow the instructions as output by 125547-02, in particular

       

      ---

      Patch 122660-10 needs to be installed before this patch can be

      successfully installed on this system.

       

      Please install 122660-10 and then run patchadd again for this patch.

      ---

       

      so apply 122660-10, followed by 125547-02

       

      Date Modified: 2007-09-24 17:53:33 GMT+00:00

       

       

      K did as recommended (installing 1226610-10 first) and patching continued correct after that.

       

      Call me picky but I think the output should be even MORE specific as this issue is ugly and confusing. The output should indicate that even though 1226610-10 is indeed obseleted it still must be installed. The output need to include the work obselete as it applies to 1226601-10 to remove any confusion or uncertainity in what the customer is expected to do.

       

      Call me picky ...

       

      Date Modified: 2007-09-26 17:45:24 GMT+00:00

       

       

      Suggested Fix:

       

      Evaluation:

       

      Fixed by patch:

       

      Integrated in Build:

       

      Duplicate of: 6606861

       

      Related Change Request(s):

       

      Date Modified: 2007-09-26 17:45:24 GMT+00:00

       

      Public Summary: