This discussion is archived
7 Replies Latest reply: Dec 5, 2012 8:09 AM by Alan_S RSS

Solaris 11/11 to 11.1 upgrade procedure

user13389509 Newbie
Currently Being Moderated
All,

I'm using a vbox s11 instance as an install server and need to upgrade it to 11.1, and then serve 11.1 from that. Having trouble working out what's actually needed.

What does the 'pre-upgrade' iso actually do and is it needed, or can you just update directly from an 11.1 repo image? Not having had two versions of S11 on an install server before, how does the 11.1 full repo co-exist with the 11/11 repo that's already there? In S10 I would simply have made another directory for it but now things aren't so clear.

Anyone done this upgrade and know what's going on?

cm/
  • 1. Re: Solaris 11/11 to 11.1 upgrade procedure
    user13389509 Newbie
    Currently Being Moderated
    OK I've applied the 'pre-upgrade' ISO contents as described in the readme. I'm inclined to stop here because I see people reporting problems in 11.1 with things I care about, principally iscsi.

    What have I in fact got now? uname -a and /etc/release are showing the same things. showrev is gone of course. I am not as a human being going to quarry each package for version info and compare it to...what?

    In short, how on earth do I figure out what it's done?

    Less and less I like IPS.

    cm/
  • 2. Re: Solaris 11/11 to 11.1 upgrade procedure
    Alan_S Explorer
    Currently Being Moderated
    user13389509 wrote:
    OK I've applied the 'pre-upgrade' ISO contents as described in the readme. I'm inclined to stop here because I see people reporting problems in 11.1 with things I care about, principally iscsi.
    I see one thread on iSCSI in the forum with 2 entries. What other issues are you concerned about?

    >
    What have I in fact got now? uname -a and /etc/release are showing the same things. showrev is gone of course. I am not as a human being going to quarry each package for version info and compare it to...what?

    In short, how on earth do I figure out what it's done?
    It's unclear what exactly you did. Did you just add the pre-upgrade packages to your local Solaris 11 repository, or did you also perform an update from there or from http://pkg.oracle.com/solaris/release?

    The version of the "entire" package will tell you if you successfully updated to Solaris 11.1:

    $ pkg list entire

    pkg list entire
    NAME (PUBLISHER) VERSION IFO
    entire 0.5.11-0.175.1.0.0.24.2 i--

    The above is what the system will show if you updated to Solaris 11.1 (0.175.1.0). If you are still showing 0.175.0, then you have not performed the update steps as documented in special notice at the top of the Solaris 11 download page:

    http://www.oracle.com/technetwork/articles/servers-storage-admin/howto-update-11dot1-ips-1866781.html


    >
    Less and less I like IPS.
    I think you really haven't used it enough to see all the benefits. I would like to recommend that you read the Solaris 10 to Solaris 11 Transition Guide, and some of the other documents and articles found in the Oracle Solaris 11 documentation.

    The full library can be found here:

    http://docs.oracle.com/cd/E26502_01/

    Other information and guides can be found here:

    http://www.oracle.com/technetwork/server-storage/solaris11/documentation/index.html

    If you can explain more what you don't like about IPS, you may get more guidance.

    -- Alan
  • 3. Re: Solaris 11/11 to 11.1 upgrade procedure
    abrante Pro
    Currently Being Moderated
    I just did a

    pkg update

    reboot

    pkg update

    reboot

    and there i was on Solaris 11.1.

    .7/M.
  • 4. Re: Solaris 11/11 to 11.1 upgrade procedure
    user13389509 Newbie
    Currently Being Moderated
    Benefits there may be with IPS but also the documentation kinda sucks.

    Now that I've played with it some I have more concrete questions:

    1. Given a repo of say Soll11 11/11 SRU12, how do you get the repo to serve out EITHER that or 11.1 as needed? Can these versions co-exist?
    2. If you can't connect the repo server to the internet, exactly what do you download from oracle to make 11.1 available, and how do you install it in the repo WITHOUT necessarily upgrading the repo server as well?
    3. How do you back out an upgrade if you're not happy with it?
  • 5. Re: Solaris 11/11 to 11.1 upgrade procedure
    Dave Miner Explorer
    Currently Being Moderated
    Answers:

    1. All versions can co-exist in any repository. You select the particular version you wish to install by specifying that version in the package(s) you install or update to.

    2. Download the repository ISO images and follow the instructions in the README file. In general there is no reason you'll need to update the repository server to serve newer versions.

    3. Not sure which kind of upgrade you're talking about. If you mean the update of the repository to a new package set, we'd suggest taking a ZFS snapshot before each update, which allows you to roll back if needed. If you mean an update of an installed system, you use beadm to activate the previous boot environment.
  • 6. Re: Solaris 11/11 to 11.1 upgrade procedure
    BLM-OSS Explorer
    Currently Being Moderated
    Here's an example of how IPS can leave a bad taste. I call this getting wedged into an incorporation spaghetti mess:

    I have followed the steps listed here for updating from the release repo to the tee. At the last step halted here. I know I could sort through this given enough time, but that's the point - a time waster. Hoping someone with x-ray vision can see through to the root problem. Perhaps not on 11 11 to start (see uname -a at bottom)? How then to roll back - a big issue in IPS, which wants to keep you rolling forward.

    root@solaris:~# pkg update be-name s11.1ga accept
    Creating Plan |
    pkg update: No solution was found to satisfy constraints
    Plan Creation: Package solver has not found a solution to update to latest available versions.
    This may indicate an overly constrained set of packages are installed.

    latest incorporations:

    pkg://solaris/consolidation/l10n/l10n-incorporation@0.5.11,5.11-0.175.1.0.0.23.1134:20120820T154803Z
    pkg://solaris/consolidation/cns/cns-incorporation@0.5.11,5.11-0.175.1.0.0.23.0:20120820T162238Z
    pkg://solaris/consolidation/ips/ips-incorporation@0.5.11,5.11-0.175.1.0.0.24.0:20120904T180327Z
    pkg://solaris/consolidation/sunpro/sunpro-incorporation@0.5.11,5.11-0.175.1.0.0.19.0:20120625T151735Z
    pkg://solaris/consolidation/osnet/osnet-incorporation@0.5.11,5.11-0.175.1.0.0.24.2:20120919T184141Z
    pkg://solaris/consolidation/install/install-incorporation@0.5.11,5.11-0.175.1.0.0.24.1736:20120912T193249Z
    pkg://solaris/consolidation/X/X-incorporation@0.5.11,5.11-0.175.1.0.0.24.1317:20120904T175757Z
    pkg://solaris/consolidation/userland/userland-incorporation@0.5.11,5.11-0.175.1.0.0.24.0:20120904T170613Z
    pkg://solaris/consolidation/nvidia/nvidia-incorporation@0.5.11,5.11-0.175.1.0.0.22.0:20120806T175117Z
    pkg://solaris/consolidation/desktop/desktop-incorporation@0.5.11,5.11-0.175.1.0.0.24.2:20120919T183843Z
    pkg://solaris/consolidation/desktop/gnome-incorporation@0.5.11,5.11-0.175.1.0.0.22.0:20120806T171142Z

    The following indicates why the system cannot update to the latest version:

    No suitable version of required package pkg://solaris/consolidation/userland/userland-incorporation@0.5.11,5.11-0.175.1.0.0.24.0:20120904T170613Z found:
    Reject: pkg://solaris/consolidation/userland/userland-incorporation@0.5.11,5.11-0.175.1.0.0.24.0:20120904T170613Z
    Reason: A version for 'incorporate' dependency on pkg:/network/dns/bind@9.6.3.7.2,5.11-0.175.1.0.0.24.0 cannot be found
    Reject: pkg://solaris/system/core-os@0.5.11,5.11-0.175.0.10.1.0.0:20120918T162729Z
    Reason: Newer version pkg://solaris/system/core-os@0.5.11,5.11-0.175.1.0.0.2.17986:20111101T191932Z is already installed
    Reject: pkg://solaris/system/library/boot-management@0.5.11,5.11-0.175.0.10.1.0.0:20120918T163655Z
    Reason: Newer version pkg://solaris/system/library/boot-management@0.5.11,5.11-0.175.1.0.0.2.1486:20111101T184558Z is already installed
    Reject: pkg://solaris/system/file-system/nfs@0.5.11,5.11-0.175.0.10.1.0.0:20120918T163025Z
    Reason: Newer version pkg://solaris/system/file-system/nfs@0.5.11,5.11-0.175.1.0.0.2.17986:20111101T192246Z is already installed
    No suitable version of required package pkg://solaris/consolidation/gnome/gnome-incorporation@0.5.11,5.11-0.151.0.1:20101105T053409Z found:
    Reject: pkg://solaris/consolidation/gnome/gnome-incorporation@0.5.11,5.11-0.151.0.1:20101105T053409Z
    Reason: A version for 'incorporate' dependency on pkg:/library/python-2/python-notify-26@0.1.1,5.11-0.151.0.1 cannot be found

    root@solaris:~# pkg list entire
    pkg list: no packages matching 'entire' installed
    root@solaris:~# pkg publisher
    PUBLISHER TYPE STATUS URI
    solaris (non-sticky) origin online http://pkg.oracle.com/solaris/release/
    root@solaris:~# uname -a
    SunOS solaris 5.11 ON11U1_03:2011-10-20 i86pc i386 i86pc
    root@solaris:~#
  • 7. Re: Solaris 11/11 to 11.1 upgrade procedure
    Alan_S Explorer
    Currently Being Moderated
    BLM-OSS wrote:
    Here's an example of how IPS can leave a bad taste. I call this getting wedged into an incorporation spaghetti mess:

    I have followed the steps listed here for updating from the release repo to the tee. At the last step halted here. I know I could sort through this given enough time, but that's the point - a time waster. Hoping someone with x-ray vision can see through to the root problem. Perhaps not on 11 11 to start (see uname -a at bottom)? How then to roll back - a big issue in IPS, which wants to keep you rolling forward.
    I don't understand this last sentence. Rolling back is easy with Solaris 11. You use the beadm command to select which boot environment you want to use. Any changes that are made during an update are made to a copy of the current BE.

    root@solaris:~# pkg list entire
    pkg list: no packages matching 'entire' installed
    If the "entire" incorporation was removed from your system, then you are not following a standard update scenario.

    root@solaris:~# pkg publisher
    PUBLISHER TYPE STATUS URI
    solaris (non-sticky) origin online http://pkg.oracle.com/solaris/release/
    root@solaris:~# uname -a
    SunOS solaris 5.11 ON11U1_03:2011-10-20 i86pc i386 i86pc
    root@solaris:~#
    And this indicates an internal development build of Solaris 11.1. What does "pkg info consolidation/osnet/osnet-incorporation" show?

    -- Alan

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points