X

News, tips, partners, and perspectives for the Oracle Solaris operating system

Warts and All!

Gerry Haskins
Director Security and Release Management

A customer once said to me that "bad news, delivered early, is
relatively good news, as it enables me to plan for contingencies". 

That need to manage expectations has stuck with me over the years.

And in that spirit, we issue Docs detailing known issues with Solaris 11 SRUs (Doc ID 1900381.1) and Solaris 10 CPU patchsets (Doc ID 1943839.1).

Many issues only occur in very specific configuration scenarios which won't be seen by the vast majority of customers.

A few will be subtle issues which have proved hard to diagnose and hence may impact a number of releases.

But providing the ability to read up on known issues before
upgrading to a particular Solaris 11 SRU or Solaris 10 CPU patchset
enables customers to make more informed and hence better decisions.

BTW: The Solaris 11 Support Repository Update (SRU) Index (Doc ID
1672221.1) provides access to SRU READMEs summarizing the goodness that
each SRU provides.  (As do the bugs fixed lists in Solaris 10 patch and
patchset READMEs.)

For example, from the Solaris 11.2 SRU10.5 (11.2.10.5.0) README:

Why Apply Oracle Solaris 11.2.10.5.0

Oracle Solaris 11.2.10.5.0 provides improvements and bug fixes that
are applicable for all the Oracle Solaris 11 systems. Some of the
noteworthy improvements in this SRU include:

  • Bug fix to prevent panics when using zones configured with exclusive
    IP networking, and DR has been used to add and remove CPUs from the
    domain (Bug 19880562).
  • Bug fix to improve NFS stability when under stress (Bug 20138331).
  • Bug fix to address the generation of FMA events on the PCIEX bus on T5-2 (Bug 20245857).
  • Bug fix to improve the performance of the zoneadm list command for systems running a large number of zones (Bug 20386861).
  • Bug fix to remove misleading warning messages seen while booting the Oracle VM Server for SPARC guests (Bug 20341341).
  • Bug fix to address NTP security issues, which includes the new slew always mode for leap second processing (Bug 20783962).
  • OpenStack components have been updated to Juno. For more information, see OpenStack Upgrade Procedures.
  • The Java 8, Java 7, and Java 6 packages have been updated. For more information, see Java 8 Update 45 Release Notes, Java 7 Update 80 Release Notes, and Java 6 Update 95 Release Notes.

Best Wishes,


Gerry

Join the discussion

Comments ( 6 )
  • guest Thursday, June 11, 2015

    Why is "Solaris 10 patches 150400-21/150401-21 and Solaris 11.2.6.4.0 may Cause pool(s) to Become SUSPENDED or a System to Panic (Doc ID 1982981.1)" missing in 1900381.1?


  • guest Thursday, June 11, 2015

    Your known issues list is missing 'Certain Solaris 11 SRUs and Solaris 10 Kernel Patches may Cause I/O Error on Failover (Doc ID 1986424.1)' IMHO


  • guest Friday, June 12, 2015

    Well spotted!

    Regarding 'Certain Solaris 11 SRUs and Solaris 10 Kernel Patches may Cause I/O Error on Failover (Doc ID 1986424.1)', the Solaris 11.2 Known Issues Doc has been updated. The impacted Solaris 10 Kernel patches were never included in the CPU patchset, so the CPU patchset Doc doesn't need updating.

    I'll investigate "Solaris 10 patches 150400-21/150401-21 and Solaris 11.2.6.4.0 may Cause pool(s) to Become SUSPENDED or a System to Panic (Doc ID 1982981.1)".

    Thanks,

    Gerry.


  • Gerry Haskins Friday, June 12, 2015

    Hi,

    The "Solaris 10 patches 150400-21/150401-21 and Solaris 11.2.6.4.0 may Cause pool(s) to Become SUSPENDED or a System to Panic (Doc ID 1982981.1)" issue *is* already referenced in both the Solaris 11 SRU and Solaris 10 CPU Known Issues docs.

    Best Wishes,

    Gerry.


  • guest Monday, November 16, 2015

    Why is "Bug 22118191 - panic in "ksslf" due to a NULL an_ctxchain_next" not mentioned in "Important Oracle Solaris 11.3 SRU Issues (Doc ID 2076753.1)" ?

    I can reproducable panic a T5120 server configured with KSSL by just pointing a Firefox Browser at it...


  • Gerry Haskins Monday, November 16, 2015

    I'm checking up on the bug you mention.

    It's a new bug, just over a couple of weeks old, with just one SR against it, and no Service Alert, which would explain why it's not in the SRU README yet.

    We document pervasive bugs in the SRU README, either where we can predict multiple customers will hit it or where there's evidence several customers have hit the issue, which is typically those with a Service Alert published against them.

    Best Wishes,

    Gerry.


Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.