
Updated: January 10, 2019

********************************************************************************

Patch-243894: Patch for OneFS 8.1.2.0. This patch addresses multiple issues 
with Protocols and Userspace.

********************************************************************************

This patch can be installed on clusters running the following OneFS version:
8.1.2.0

This patch deprecates the following patches:
Patch-242854
Patch-241947
Patch-241940
Patch-240163
Patch-239343
Patch-236288

This patch will conflict with the following patches:
Patch-243896
Patch-240798
Patch-239260

If any conflicting or deprecated patches are installed on the cluster, you must
remove them before installing this patch.

********************************************************************************

RESOLVED ISSUES

The patch includes new fixes for the following vulnerabilities:

* Bug ID 242390
  The HTTP response header disclosed version information about the server, 
  middleware components and/or application platform framework.
  
* Bug ID 234577
  The mountd process could have disclosed the existence of files to remote users 
  who were denied access to an export.
  
The patch includes previous fixes for the following vulnerabilities:

* Bug ID 242377
  During system auditing, if the audit message was too long, services could be 
  temporarily unavailable.

* Bug ID 241873
  OneFS was affected by an elevation of privilege vulnerability where an 
  attacker with an admin role could have run commands as root.  

  For more information about this issue, see DSA-2018-221 on the Customer 
  support site.

* Bug ID 241294
  The version of SQLite3 was updated to 3.24.0. This version addresses 
  multiple bugs and CVE-2018-8740, CVE-2017-15286, CVE-2017-13685, 
  CVE-2017-10989, CVE-2016-6153, CVE-2015-6607, CVE-2015-5895, CVE-2015-3717, 
  CVE-2015-3416, CVE-2015-3415, CVE-2015-3414. 

  For more information about these CVEs, see DSA-2018-221 on the Customer 
  support site.

The patch includes the following other fixes:  

* Bug ID 242185 
  To avoid lock leak issues, support “Complete” with File ID in addition 
  to the path name, so that files would be completed successfully when they
  are renamed.  

* Bug ID 241864
  Hadoop Distributed File System (HDFS) RPCs that did not require
  a lock from being blocked behind lock checkers should be prevented.

* Bug ID 241098
  WebHDFS REST API returned IP outside of the Hadoop Distributed File
  System (HDFS) rack IP Pool.

* Bug ID 240177
  The Hadoop Distributed File System (HDFS) rename command did not manage
  file handles correctly and might have caused data unavailability
  with STATUS_TOO_MANY_OPEN_FILES error.
  
* Bug ID 237032
  Open state table entry with state NFS4_OPEN_STATE_UNCONFIRMED
  caused the client to spin forever.

* Bug ID 236286
  If a OneFS cluster had the Hadoop Distributed File System (HDFS) configured 
  for Kerberos authentication, WebHDFS requests over curl might have failed to 
  follow a redirect request.

* Bug ID 235646
  When you used commands like ls or rsync on dir through NFSv3 and NFSv4, 
  a huge performance gap was noticed in readdir. NFSv4 triggered extra lock
  requests from readdir, particularly the ones that impacted performance.

* Bug ID 235463  
  The isi_phone_home tool did not create /data and /data/<lnn> directories for 
  clusters that were upgraded to 8.1.0.4 and already had IPH enabled. Logging 
  also failed for per node telemetry when the LNN did not match the DevID.
  
* Bug ID 234049
  An NFSv4 mount issue was resolved.

* Bug ID 232835
  If you tried to access a OneFS cluster through SMB and the MaxdataCount was
  set to (-1), lwio might have failed on FSCTL_SRV_ENUMERATE_SNAPSHOTS.
  
* Bug ID 231111
  NFS traffic (default 2049) to a OneFS cluster’s
  Network Lock Manager (NLM) port (default 304),including NULL was not 
  blocked. As a result, unauthorized users could still perform NFS queries 
  through the nlockmgr (RPC) service.
  
* Bug ID 229065
  When files were created with large access control lists (ACLs), memory leak
  was found in OnefsGetSecurityDescriptorFile.
  
********************************************************************************

CHANGED FILES

* /etc/mcp/templates/apache24.conf
  (MD5 = 5e9b06f90ad44b5ef4a6db716f658e24)

* /etc/mcp/templates/sudoers
  (MD5 = 22f2c86706bef012dca1103099458f0e)

* /etc/mcp/templates/webui_httpd.conf
  (MD5 = bb87e06bdb96f4b8264a9794d41729ae)

* /usr/lib/libisi_audit.so.1
  (MD5 = aa63dbbbeba170bc7132f97f89c208f0)

* /usr/lib/libisi_flt_audit.so.1
  (MD5 = 1a7850a91d050be49bac1d393d603666)

* /usr/lib/libisi_qpl.so.1
  (MD5 = 3cff074a318aac4ea8e4c0aa915bdb6e)

* /usr/lib/libisi_rest_server.so.1
  (MD5 = e782d27beceebd6119c8bfeba03a84de)

* /usr/likewise/lib/libfsp_hdfs_ambari.so.0
  (MD5 = 429da8ea559568ce0db9b61ed89758fe)

* /usr/likewise/lib/libfsp_hdfs_driver.so.0
  (MD5 = 8033655a3b9cde4d78f0eb8c10e3f85a)

* /usr/likewise/lib/libfsp_hdfs_filesystem.so.0
  (MD5 = 72482b0fd785cb8b950927fd498bad39)

* /usr/likewise/lib/libfsp_hdfs_lw_fsimage.so.0
  (MD5 = 48326503e54f3651f010f37d9c0a0998)

* /usr/likewise/lib/libfsp_hdfs_lwio_journal.so.0
  (MD5 = 31689e990c59915b54ae6baf1b685435)

* /usr/likewise/lib/libfsp_hdfs_lwpp_ioapi.so.0
  (MD5 = 9bac5b8951d8747dad71fb2370abfc9d)

* /usr/likewise/lib/libfsp_hdfs_objects.so.0
  (MD5 = 1254d9ce0d33e1404e1b85751f9fb63f)

* /usr/likewise/lib/libfsp_hdfs_protocols.so.0
  (MD5 = 73b2a391c68800ce226057a61cd2d4d8)

* /usr/likewise/lib/libfsp_hdfs_ranger.so.0
  (MD5 = 38e9efb5bb4b7671b97d787767956bb2)

* /usr/likewise/lib/libfsp_hdfs_zone.so.0
  (MD5 = 0e724251d3fd60d9c8ebdcfb0d95ddb4)

* /usr/likewise/lib/libisilon_registry_gcfg.so.0
  (MD5 = ab6d100667a5c91922f12b0da8a4de17)

* /usr/likewise/lib/liblwnfsmgmt_clnt.so.0
  (MD5 = 4a0c3e9a92a520eec8ddd7d80b481b7f)

* /usr/likewise/lib/lw-svcm/hdfs.so
  (MD5 = 09bffad6827d6f07b38a4373a4ffe464)

* /usr/likewise/lib/lw-svcm/nfs.so
  (MD5 = 3b82eb0de7ce36e02bdefe90cc080b14)

* /usr/likewise/lib/lw-svcm/onefs.so
  (MD5 = 3822d1053905123af1666b70b4610543)

* /usr/likewise/lib/lw-svcm/srv.so
  (MD5 = 983ed47eea262cf38e26f3953478afe4)

* /usr/likewise/share/config/nfs.reg
  (MD5 = 355d2e217c1b471ce3401314fe695a44)

* /usr/local/isi_phone_home/isi_phone_home
  (MD5 = c177f124a5098b97b98b807827ff9392)

* /usr/local/lib/python2.7/site-packages/isi/audit/qpl.so
  (MD5 = a74792fe91d564b3dbc096fb8b728453)

* /usr/sbin/isi_tardis_d
  (MD5 = 5189d012f670f6b20e657496c6d14fb8)

********************************************************************************

INSTALLATION/REMOVAL IMPACTS

During installation or removal of this patch, the following services will be 
stopped and restarted automatically:

* isi_group_change_d 
* celog 
* isi_tardis_gcfg_d 
* isi_cpool_io_d 
* isi_cpool_d 
* isi_object_d 
* hdfs 
* isi_hangdump 
* lwswift 
* isi_webui 
* isi_papi_d 
* ndmpd 
* apache2 
* isi_km_d 
* isi_migrate 
* isi_drivemon 
* isi_smartpools_d 
* isi_tardis_d 
* isi_drive_repurpose_d 
* isi_audit_cee 
* isi_audit_syslog 
* isi_job_d 
* isi_audit_d 
* isi_upgrade_d 
* nfs

When a patch requires that services be restarted, by default, the 'isi
upgrade patches install' command performs a rolling reboot of all nodes in the
cluster to restart the affected services. If a rolling reboot is performed,
client connections to the cluster over protocols that are configured or 
designed to fail over to another node are not disconnected. However, client
connections to the cluster over other protocols are disconnected when the node
they are connected to reboots. Clients that are disconnected must manually
reestablish a connection to the cluster.

You can also configure the command to install the patch on all nodes in the
cluster simultaneously by running the 'isi upgrade patches install' command
with the '--rolling=false' parameter. If you perform a simultaneous
installation of the patch, nodes are not rebooted. However, services that are
affected by the patch are simultaneously restarted on all nodes in the cluster.
If services are restarted, clients and cluster operations that require those
services are temporarily disrupted while the service restarts.

EMC Isilon recommends that you install the patch during an off-hours 
maintenance window to minimize the disruption of service to clients.

********************************************************************************

IMPORTANT!
VERIFY CLUSTER-FREE SPACE
If there is insufficient free space and you attempt to install or remove a
patch, the process might not complete successfully. An incomplete patch
installation or patch removal can leave the cluster in an inaccessible state.

Before installing or removing a patch, verify that your cluster has enough
free space to perform the procedure. For more information about maintaining
sufficient free space on an Isilon cluster, see the Best Practices Guide for
Maintaining Enough Free Space on Isilon Clusters and Pools:
https://support.emc.com/docu48119.

********************************************************************************

PRE INSTALLATION INSTRUCTIONS

REMOVING CONFLICTING AND DEPRECATED PATCHES

If any conflicting or deprecated patches are installed on the cluster,
perform the following procedure to remove them before installing this patch.

IMPORTANT!
Read the INSTALLATION/REMOVAL IMPACTS in the README for the
conflicting and deprecated patches before performing this procedure.

1. Verify that your cluster has enough free space to remove this patch.

2. Open an SSH connection on any node in the cluster and log in using the
   root account.

   NOTE: If the procedure is being done on a compliance mode cluster,
   log in using the compadmin account.

3. To remove this patch, run the following command, where <ID> is the patch ID
   of the patch to be removed:

   isi upgrade patches uninstall patch-<ID> --rolling=false

   NOTE: The preceding command updates all of the nodes in the cluster
   simultaneously, and then restarts the affected services on all of the
   nodes simultaneously. To remove the patch and then reboot each node in
   succession, omit the '--rolling=false' parameter. For more information,
   see the Installation/Removal Impacts section of the README.

   Confirm that you want to continue with this operation:

   Are you sure?  (yes/[no]): yes

4. To verify that this patch was removed, run the following command:

   isi upgrade patches list

5. Confirm that patch-<ID> does not appear in the list of installed packages.

********************************************************************************

INSTALLING THIS patch
Follow these instructions to install the patch.

IMPORTANT!
Read INSTALLATION/REMOVAL IMPACTS before performing this procedure.

1. Verify that your cluster has enough free space to install this patch.

2. Open an SSH connection on any node in the cluster and log in by using the
   root account.

   NOTE: If the patch is being installed on a compliance mode cluster,
   log in using the compadmin account.

3. Copy the patch-243894.tgz file to the /ifs/data directory on the cluster.

4. Run the following command to change to the /ifs/data directory:

   cd /ifs/data

5. To extract the patch file, run the following command:

   tar -zxvf patch-243894.tgz

6. To install this patch, run the following command:

   isi upgrade patches install patch-243894.pkg --rolling=false

   NOTE: The preceding command updates all of the nodes in the cluster
   simultaneously, and then restarts the affected services on all of the
   nodes simultaneously. To install the patch and then reboot each node in
   succession, omit the '--rolling=false' parameter. For more information,
   see the Installation/Removal Impacts section of the README.

7. To verify that this patch is installed, run the following command:

   isi upgrade patches list

8. Confirm that patch-243894 appears in the list of installed packages and the
   status is set to Installed.

********************************************************************************

REMOVING THIS patch

If you need to remove this patch, complete the steps below.

IMPORTANT!
Read INSTALLATION/REMOVAL IMPACTS before performing this procedure.

1. Verify that your cluster has enough free space to remove this patch.

2. Open an SSH connection on any node in the cluster and log in using the
   root account.

   NOTE: If the procedure is being done on a compliance mode cluster,
   log in using the compadmin account.

3. To remove this patch, run the following command:

   isi upgrade patches uninstall patch-243894 --rolling=false

   NOTE: The preceding command updates all of the nodes in the cluster
   simultaneously, and then restarts the affected services on all of the
   nodes simultaneously. To uninstall the patch and then reboot each node in
   succession, omit the '--rolling=false' parameter. For more information,
   see the Installation/Removal Impacts section of the README.

4. To verify that this patch is removed, run the following command:

   isi upgrade patches list

5. Confirm that patch-243894 does not appear in the list of installed packages.

********************************************************************************

TROUBLESHOOTING THIS patch

If you received the following output after running the 'isi upgrade patches
list' command during installation or removal of this patch, follow the
additional instructions below.

# isi upgrade patches list
patch Name   Description                           Status
patch-243894 ...                                   Failed
Total: 1

1. Run the following command to create a statuscache file on the cluster:

   isi_upgrade_status > /ifs/.ifsvar/upgrade/statuscache

2. Run the following command to attempt the patch installation or removal
   procedure again:

   isi upgrade retry-last-action --nodes=all

3. Wait five minutes for the commands to take effect.

4. Run the following command to verify that this patch is installed or removed:

   isi upgrade patches list

5. Confirm that patch-243894 appears (or does not appear, if the patch is
   being removed) in the list of installed packages and the status is set to
   Installed.

6. Should the patch status fail again, please contact Isilon Technical Support
   for further troubleshooting steps.

********************************************************************************
