Add some known issues that are tied to the OpenBMC firmware

docs/source/references/coral/known_issues/index.rst

@@ -5,3 +5,4 @@ Known Issues
    :maxdepth: 2
 
    genesis_base.rst
+   openbmc/index.rst

docs/source/references/coral/known_issues/openbmc/SW402273.rst

@@ -0,0 +1,17 @@
+SW402273 - Unable to tell the firmware level that is actually running on the node via REST
+==========================================================================================
+
+* **Issue:** `SW402273 <https://w3.rchland.ibm.com/projects/bestquest/?defect=SW402273>`_
+* **Reported:** 1738B (ibm-v1.99.10-0-r7)
+* **Fixed:** 1740B (ibm-v1.99.10-0-r13)
+
+**Issue:** 
+
+Until 1740B firmware (> ibm-v1.99.10-0-r13), there's no method provided by OpenBMC to indicate the active running firmware on the node.  Until the BMC is rebooted or the HOST is rebooted, the Active firmware may or may not really be running. 
+
+If you are running a version that prints the following message from ``rflash``:  ::
+
+    cn01: WARNING, The current firmware is unable to detect running firmware version.
+
+Please update the BMC to a version higher than ibm-v1.99.10-0-r13.
+

docs/source/references/coral/known_issues/openbmc/SW404161.rst

@@ -0,0 +1,26 @@
+SW404161 - Firmware do not self extract tar, causing rflash cannot find ID to activate
+======================================================================================
+
+* **Issue:** `SW404161 <https://w3.rchland.ibm.com/projects/bestquest/?defect=SW404161>`_
+* **Reported:** 1738A (ibm-v1.99.10-0-r7)
+* **Fixed:** 1742D (ibm-v1.99.10-0-113-r10)
+
+**Issue:** 
+
+Firmware is not extracted and could not be found by rflash to activate ::
+
+    [root@c650mnp03 ~]# rflash c650f07p27 obmc-phosphor-image-witherspoon.ubi.mtd.tar -a
+    c650f07p27: Uploading /root/obmc-phosphor-image-witherspoon.ubi.mtd.tar ...
+    c650f07p27: Firmware upload successful. Attempting to activate firmware: ibm-v1.99.10-113-g65edf7d-r8-0-g713d86d
+    c650f07p27: Could not find ID for firmware ibm-v1.99.10-113-g65edf7d-r8-0-g713d86d to activate, waiting 10 seconds and retry...
+    c650f07p27: Could not find ID for firmware ibm-v1.99.10-113-g65edf7d-r8-0-g713d86d to activate, waiting 10 seconds and retry...
+    c650f07p27: Could not find ID for firmware ibm-v1.99.10-113-g65edf7d-r8-0-g713d86d to activate, waiting 10 seconds and retry...
+    c650f07p27: Could not find ID for firmware ibm-v1.99.10-113-g65edf7d-r8-0-g713d86d to activate, waiting 10 seconds and retry...
+    c650f07p27: Could not find ID for firmware ibm-v1.99.10-113-g65edf7d-r8-0-g713d86d to activate, waiting 10 seconds and retry...
+    c650f07p27: Could not find ID for firmware ibm-v1.99.10-113-g65edf7d-r8-0-g713d86d to activate, waiting 10 seconds and retry...
+    c650f07p27: Error: Could not find firmware ibm-v1.99.10-113-g65edf7d-r8-0-g713d86d after waiting 60 seconds.
+
+**Work-around:** Use one of the following methods: 
+
+* Reboot the BMC before flashing firmware: ``rpower <> bmcreboot``
+* ssh into bmc and run:  ``systemctl restart xyz.openbmc_project.Software.Version.service``

docs/source/references/coral/known_issues/openbmc/SW406960.rst

@@ -0,0 +1,18 @@
+SW406960 - On first REST call after rebooting BMC, 503: Unavailable is returned
+===============================================================================
+
+* **Issue:** `SW406960 <https://w3.rchland.ibm.com/projects/bestquest/?defect=SW406960>`_
+* **Reported:** 1742C (ibm-v1.99.10-113-g65edf7d-r8-0-g713d86d)
+* **Fixed:** No ETA
+
+**Issue:** 
+
+First call after BMC is rebooted results in ``503`` Error ::
+
+    [root@briggs01 openbmc]# rpower mid05tor12cn05 state
+    mid05tor12cn05: Error: 503 Service Unavailable
+
+**Work-around:** Run the command again: ::
+
+    [root@briggs01 openbmc]# rpower mid05tor12cn05 state
+    mid05tor12cn05: on

docs/source/references/coral/known_issues/openbmc/SW407037.rst

@@ -0,0 +1,38 @@
+SW407037 - bmcsetup does not successfully configure the IP (Sev1)
+=================================================================
+
+* **Issue:** `SW407037 <https://w3.rchland.ibm.com/projects/bestquest/?defect=SW407037>`_
+* **Reported:** 1742C (ibm-v1.99.10-113-g65edf7d-r8-0-g713d86d)
+* **Fixed:** Fixed in xCAT after 11/07/17 `#4242 <https://github.com/xcat2/xcat-core/issues/4242>`_ 
+
+**Issue:** 
+
+OpenBMC firmware has problems with ipmi inband support of the ``access on`` comamnd and the work around is to use the ``raw 0x06 0x40`` instead.  In early Sept, we switched to using ``access on`` because the implementation looked like it was working, since then we have found some issues with it and recommendation is to revert back to the raw command. 
+
+See related issues describing potential problems:
+* https://github.com/openbmc/openbmc/issues/2493
+* https://github.com/openbmc/openbmc/issues/2492
+
+This problem is very severe because if the network is not configured correctly, the access to the BMC is lost. 
+
+**Work-around**
+
+Use one of the following work arounds: 
+
+#.  Install a version of xCAT built after November, 07, 2017 which includes the fix. (**Recommended**)
+
+#.  Manually patch bmcsetup using changes in PR: https://github.com/xcat2/xcat-core/pull/4247, then run ``mknb ppc64``
+
+#.  Patch the system with provided patch: 
+
+    #. Download patch file: https://github.com/xcat2/xcat-core/files/1451181/bmcsetup.4242.patch.txt
+
+    #. If file name is ``/tmp/bmcsetup.4242.patch.txt``
+
+    #. ``cd /opt/xcat/share/xcat/netboot/genesis/ppc64/fs/usr/bin``
+
+    #. ``patch -p0 < /tmp/bmcsetup.4242.patch.txt``
+ 
+    #. ``mknb ppc64``
+
+

docs/source/references/coral/known_issues/openbmc/index.rst

@@ -0,0 +1,23 @@
+OpenBMC Firmware Issues 
+=======================
+
+The following versions indicate the level of firmware the issue was reported. 
+
+
+1742C - ibm-v1.99.10-113-g65edf7d-r8-0-g713d86d
+-----------------------------------------------
+
+.. toctree::
+   :maxdepth: 2
+
+   SW407037.rst
+   SW406960.rst
+
+1738A -  ibm-v1.99.10-0-r7
+--------------------------
+
+.. toctree::
+   :maxdepth: 2
+
+   SW404161.rst
+   SW402273.rst