Mandalika's scratchpad [ Work blog @Oracle | Stock Market Notes | My Music Compositions ]

Old Posts: 09.04  10.04  11.04  12.04  01.05  02.05  03.05  04.05  05.05  06.05  07.05  08.05  09.05  10.05  11.05  12.05  01.06  02.06  03.06  04.06  05.06  06.06  07.06  08.06  09.06  10.06  11.06  12.06  01.07  02.07  03.07  04.07  05.07  06.07  08.07  09.07  10.07  11.07  12.07  01.08  02.08  03.08  04.08  05.08  06.08  07.08  08.08  09.08  10.08  11.08  12.08  01.09  02.09  03.09  04.09  05.09  06.09  07.09  08.09  09.09  10.09  11.09  12.09  01.10  02.10  03.10  04.10  05.10  06.10  07.10  08.10  09.10  10.10  11.10  12.10  01.11  02.11  03.11  04.11  05.11  07.11  08.11  09.11  10.11  11.11  12.11  01.12  02.12  03.12  04.12  05.12  06.12  07.12  08.12  09.12  10.12  11.12  12.12  01.13  02.13  03.13  04.13  05.13  06.13  07.13  08.13  09.13  10.13  11.13  12.13  01.14  02.14  03.14  04.14  05.14  06.14  07.14  09.14  10.14  11.14  12.14  01.15  02.15  03.15  04.15  06.15  09.15  12.15  01.16  03.16  04.16  05.16  06.16  07.16  08.16  09.16  12.16  01.17  02.17  03.17  04.17  06.17  07.17  08.17  09.17  10.17  12.17  01.18  02.18  03.18  04.18  05.18 


Tuesday, February 27, 2018
 
Steps to Upgrade from Solaris 11.3 to 11.4 Beta

Recently I updated one of our lab systems running Solaris 11.3 SRU 16 to Solaris 11.4 beta. Just wanted to share my experience along with the steps I ran and the outputs/stdout/stderr messages that I captured. I followed Updating Your Operating System to Oracle Solaris 11.4 document in Solaris 11.4 documentation library and the instructions worked flawlessly without a hitch.

My target system has one non-global zone running, and it took a little over one hour to complete the upgrade from start to finish. I recommend setting at least couple of hours aside for this upgrade as various factors such as the current Solaris 11.3 SRU, number of non-global zones running, and how Solaris 11.4 Beta packages are being accessed have a direct impact on the overall time it takes to complete the upgrade exercise.

Step 1: Prepare the System for Upgrade

Oracle recommends that the target system is at least at Solaris 11.3 SRU 23 level for the upgrade to succeed so the first step is to make sure that the system is running Solaris 11.3 SRU 23 or later.

eg.,
# pkg info entire | grep -i branch
           Branch: 0.175.3.16.0.3.0

The above output indicates that my lab system is running Solaris 11.3 SRU 16 - so, I have no choice but to upgrade 11.3 SRU first. Those with systems already at 11.3 SRU 23 or later can skip to Step 2: Get access to Solaris 11.4 Beta packages.

Following listing indicates that existing/configured publishers allow me to upgrade 11.3 to the latest SRU (which is 29).

# pkg list -af entire@0.5.11-0.175.3
NAME (PUBLISHER)             VERSION                    IFO
entire (solaris)             0.5.11-0.175.3.29.0.5.0    ---
entire (solaris)             0.5.11-0.175.3.28.0.4.0    ---
...

An attempt to update my system to the latest SRU met with a failure.

# pkg update --be-name s11.3.sru29 pkg:/entire@0.5.11-0.175.3.29.0.5.0
            Packages to remove:  37
           Packages to install:  12
            Packages to update: 510
       Create boot environment: Yes
Create backup boot environment:  No

Planning linked: 0/1 done; 1 working: zone:some-ngz
Linked progress: /pkg: update failed (linked image exception(s)):

A 'sync-linked' operation failed for child 'zone:some-ngz' with an 
unexpected return value of 1 and generated the following output:

pkg sync-linked: One or more client key and certificate files have 
expired. Please update the configuration for the publishers or origins 
listed below:

Publisher: solarisstudio
  Origin URI:
    https://pkg.oracle.com/solarisstudio/release/
    ...

Root cause of this failure is that a seperate repo for Solaris Studio has been configured in the non-global zone. Fixed it by removing associated publisher from the non-global zone.

root@some-ngz:~# pkg publisher
PUBLISHER                   TYPE     STATUS P LOCATION
solaris        (syspub)     origin   online T 
solarisstudio  (syspub)     origin   online T 
solarisstudio  (syspub)     origin   online F https://pkg.oracle.com/solarisstudio/release/

root@some-ngz:~# pkg set-publisher -G https://pkg.oracle.com/solarisstudio/release/ solarisstudio

SRU update has no problem afterward.

# pkg update --be-name s11.3.sru29 pkg:/entire@0.5.11-0.175.3.29.0.5.0
            Packages to remove:  37
           Packages to install:  12
            Packages to update: 510
       Create boot environment: Yes
Create backup boot environment:  No

Planning linked: 0/1 done; 1 working: zone:some-ngz
Linked image 'zone:some-ngz' output:
|  Packages to remove:  25
| Packages to install:  12
|  Packages to update: 237
|  Services to change:   9
`
...
Updating image state                            Done
Creating fast lookup database                   Done
Executing linked: 0/1 done; 1 working: zone:some-ngz
Executing linked: 1/1 done
Updating package cache                           3/3

A clone of s11.3.sru.16.3.0 exists and has been updated and activated.
On the next boot the Boot Environment s11.3.sru29 will be
mounted on '/'.  Reboot when ready to switch to this updated BE.

Now that the system was upgraded to 11.3 SRU 29, it is time to boot the new boot environment (BE) in preparation for a subsequent upgrade to 11.4 beta.

# beadm list | grep sru29
s11.3.sru29        R     -          98.05G  static 2018-02-26 17:13

# shutdown -y -g 30 -i6

# pkg info entire | grep -i branch
           Branch: 0.175.3.29.0.5.0

Step 2: Get access to Solaris 11.4 Beta packages

Unless the target system has no connectivity to the public pkg.oracle.com repo, probably the simplest way is to use the public package repository that was set up by Oracle to support 11.4 beta. If the preference is to have a local repository for any reason (say no exernal connectivity, control what gets installed for example), download the Solaris 11.4 Beta package repository file and follow the instructions in README to set up the beta repository locally.

Rest of this section shows the steps involved in getting access to the public repository.

Step 3: Perform the Upgrade

Optionally perform a dry run update to check if there are any issues.

pkg update -nv

Finally perform the actual update to Solaris 11.4. This is the most time consuming step in this whole exercise.

# pkg update --accept --be-name 11.4.0 --ignore-missing \
  --reject system/input-method/ibus/anthy \
  --reject system/input-method/ibus/pinyin \
  --reject system/input-method/ibus/sunpinyin \
  --reject system/input-method/library/m17n/contrib entire@latest
            ...
            Packages to remove: 190
           Packages to install: 304
            Packages to update: 716
           Mediators to change:   8
       Create boot environment: Yes
Create backup boot environment:  No
           ...

Reboot the system to boot the new 11.4 boot environment and check the OS version.

# uname -v
11.3

# beadm list | grep R
11.4.0             R     -          113.20G static 2018-02-26 20:10

# shutdown -y -g 30 -i6

# uname -v
11.4.0.12.0

# pkg info entire | grep Version
          Version: 11.4 (Oracle Solaris 11.4.0.0.0.12.1)

Labels:




Comments: Post a Comment

Links to this post:

Create a Link



<< Home


2004-2018 

This page is powered by Blogger. Isn't yours?