Upgrading to a New OmniOS Release

The following table shows the supported upgrade paths between OmniOS versions.

Upgrading from versions not listed below has not been tested and is not supported.

From Release   To Release(s)
r151022 (OmniTI version) r151022 (LTS), r151024 (stable) (See note below)
r151022 (LTS) r151024, r151026, r151028 (stable), r151030 (LTS)
r151024 (stable) r151026, r151028 (stable), r151030 (LTS)
r151026 (stable) r151028 (stable), r151030 (LTS)
r151028 (stable) r151030 (LTS)
r151030 (LTS) r151032, r151034, r151036 (stable), r151038 (LTS)
r151032 (stable) r151034, r151036 (stable), r151038 (LTS)
r151034 (stable) r151036 (stable), r151038 (LTS)
r151036 (stable) r151038 (LTS)
r151038 (LTS) r151040, r151042, r151044 (stable), r151046 (LTS)
r151040 (stable) r151042, r151044 (stable), r151046 (LTS)
r151042 (stable) r151044 (stable), r151046 (LTS)
r151044 (stable) r151046 (LTS)
r151046 (LTS) r151048 (stable), r151050 (stable)
r151048 (stable) r151050 (stable)
Before upgrading, check that you have removed any legacy options from your OpenSSH configuration file . Failure to do so may result in the SSH service not starting after upgrade.

Performing the Upgrade

The upgrade process creates a clone of the current boot environment in order to upgrade it. Any changes made to the current boot environment after the update is started will be lost once you reboot into the new one. This includes changes to log files so you may wish to disable services that produce data or log entries that you don’t want to lose before starting.

  • Make sure the global zone can reach the network.

  • Create a backup boot environment for safety:
    # beadm create <appropriate-backup-name>
  • Change the publisher in the global zone and all linked zones (e.g. lipkg and sparse branded zones). For example, going to r151050:
    # pkg set-publisher -r -O https://pkg.omnios.org/r151050/core omnios
    # pkg set-publisher -r -O https://pkg.omnios.org/r151050/extra extra.omnios
  • Shut down and detach any ipkg branded zones (NB: linked zones such as the lipkg and sparse brands do not need to be detached):
    # zoneadm -z <zonename> shutdown
    ... use the following command to check when the zone has shut down ...
    # zoneadm -z <zonename> list -v
    # zoneadm -z <zonename> detach

    It is also a good idea to take a ZFS snapshot of the zone root in case it’s needed for rollback (such as if there are issues with the zone upgrade.)

    # zfs snapshot -r /path/to/zone@<old-release>
  • Perform the update, optionally specifying the new boot-environment name:
    # pkg update -f -r --be-name=r151050

    This will create a new BE and install the new packages into it. When this is complete, reboot your system. The new BE will now be the default option in loader.

  • Reboot
    # init 6
  • Re-attach any ipkg zones:
    # zoneadm -z <zonename> attach -u


In case a boot environment (BE) is not updating to the latest release, try to enable an older BE (in the example below omnios-r151044) and reboot. Then, update the BE. Make sure to use a new BE for the update.

For example:

# beadm activate omnios-r151044
# init 6
# pkg update -f -r --be-name=r151050 

Installing the OmniOS CA Certificate

If upgrading from OmniTI OmniOS first install the OmniOS CA certificate:

# wget -P /etc/ssl/pkg https://downloads.omnios.org/ssl/omniosce-ca.cert.pem
# openssl x509 -fingerprint -in /etc/ssl/pkg/omniosce-ca.cert.pem -noout
SHA1 Fingerprint=8D:CD:F9:D0:76:CD:AF:C1:62:AF:89:51:AF:8A:0E:35:24:4C:66:6D