Originated: December 10, 2015
Updated: January 15, 2016
********************************************************************************

Patch-164327: Patch for OneFS 7.2.1.1. This patch addresses an issue in which, 
if a cluster cannot contact a writeable Windows 2008 R2 or later domain 
controller, attempts to failover to a read-only domain controller fail, and a 
KRB_AP_ERR_BAD_INTEGRITY error is returned to the cluster. This patch also
addresses an issue where LDAP can only be queried for the default base_dn field
user list, even when a user- or group-specific base_dn field exists on the LDAP
server.

--------------------------------------------------------------------------------

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

This patch deprecates the following patch:
patch-161462

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

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

RESOLVED ISSUES

* Bug ID 160417
  If a cluster was not able to contact a writeable Windows 2008 R2 or later 
  Domain Controller (DC), attempts to failover to a read-only domain controller 
  failed and a KRB_AP_ERR_BAD_INTEGRITY error was returned to the cluster. This 
  issue occurred because the name-type sent in the Kerberos Ticket-Granting 
  Ticket request was not KRB5-NT-SRV-INST, which is the required name-type
  for compatibility in this environment. As a result, clients connected to the 
  cluster could have experienced intermittent authentication issues.

* Bug ID 162437
  If you configured the user or group query settings for an LDAP authentication
  provider, so that user and group queries were restricted to a distinguished
  name that differed from the base distinguished name (base_dn), the
  configuration setting was not honored. As a result, user and group LDAP
  queries returned the full list of users or groups found in the base_dn. For
  example, if you configured an LDAP provider with the base_dn of
  "dc=my_company,dc=com" and you configured user queries to be performed against
  the distinguished name "ou=people,dc=my_company,dc=com", user queries were
  performed against "dc=my_company,dc=com".
 
********************************************************************************

CHANGED FILES

* /usr/lib/libkrb5.so.3
  (MD5 = c4f3e47629392a97ec2d04953d7ce505)
  
* /usr/likewise/lib/lsa-provider/ldap.so
  (MD5 = 9487dd8778463c46e44087bce43db93a)

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

INSTALLATION/REMOVAL IMPACTS

During installation or removal of this patch, the SMB and authentication
services are unavailable and SMB client connections to the cluster are
disconnected. After the patch is installed, SMB clients must reestablish
a connection to the cluster.

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

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.

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

REMOVE DEPRECATED PATCHES

If any 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 deprecated patch 
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 pkg delete patch-<ID>

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

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

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

INSTALLING THIS 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.
   
   Run the following command to list the running lw processes and make a
   note of the PID for each process:

   isi_for_array -sI "ps -ax | grep lw | grep -v grep"

   Information similar to the following appears, where the value listed in the
   PID column is the PID of the related lw process.

   Node    PID               Time    Process name
   clus-1: 63688  ??  I      0:02.75 lw-container lwreg (lwreg)
   clus-1: 63689  ??  I      0:00.25 lw-container netlogon (netlogon)
   clus-1: 63691  ??  S      0:14.06 lw-container lsass (lsass)
   clus-1: 63703  ??  I      0:00.32 lw-container srvsvc (srvsvc)
   clus-1: 63742  ??  I      0:02.65 lw-container lwio (lwio)
   clus-2: 40114  ??  I      0:02.75 lw-container lwreg (lwreg)
   clus-2: 40115  ??  I      0:00.25 lw-container netlogon (netlogon)
   clus-2: 40120  ??  S      0:14.06 lw-container lsass (lsass)
   clus-2: 40121  ??  I      0:00.32 lw-container srvsvc (srvsvc)
   clus-2: 40122  ??  I      0:02.65 lw-container lwio (lwio)

4. To shut down the lw processes, disable the Likewise Service Manager (lwsm)
   service: 

   isi services -a lwsm disable

5. Wait 30 seconds, and then run the following command to confirm that the
   lw processes are not running on any nodes:  

   isi_for_array -sI "ps -ax | grep lw | grep -v grep"   

   Nodes that are not running lw services will return the following when
   you run the ps command using the isi_for_array command. 
   
   node-1 exited with status 1
   node-3 exited with status 1
   
   Nodes that are running lw services will return information similar 
   to the following.
   
   NOTE: The PID values are listed in the table below, under the PID header.

   Node    PID               Time    Process name
   clus-2: 46234  ??  I      0:00.05 /usr/likewise/sbin/lwsmd --syslog
    --start-as-daemon
   clus-2: 46245  ??  I      0:00.18 lw-container lwreg (lwreg)
   clus-2: 46246  ??  S      0:00.04 lw-container netlogon (netlogon)
   clus-2: 46247  ??  S      0:00.12 lw-container lwio (lwio)
   clus-2: 46248  ??  S      0:00.41 lw-container lsass (lsass)
   clus-2: 46331  ??  I      0:00.03 /usr/likewise/bin/lwsm proxy nfs
   clus-2: 46339  ??  I      0:00.13 lw-container nfs (nfs)
   clus-2: 46350  ??  I      0:00.07 lw-container srvsvc (srvsvc)

   It can take time for the processes to be stopped. Wait 30 seconds and run 
   the ps command again.

6. If, after five minutes, the lw processes are still running, run the
   following command to stop the remaining lw processes, where <node#> is
   the number of the node on which the processes are still running, and
   <PID> is the PID of the lw process that needs to be stopped.  
 
   isi_for_array -n <node#> kill <PID>

7. Run the following command again to confirm that the remaining lw
   processes have stopped:

   isi_for_array -sI "ps -ax | grep lw | grep -v grep"   

   When all the lw processes have stopped running, proceed to the next step.
   Otherwise, repeat the previous step and this step until there are no more
   lw processes running. 

8. Copy the patch-164327.tgz file to the /ifs/data directory on the cluster.

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

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

   tar -zxvf patch-164327.tgz

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

   isi pkg install patch-164327.tar

12. To verify that this patch is installed, run the following command:
  
   isi pkg info
   
13. Confirm that patch-164327 appears in the list of installed packages.

14. Run the following command to enable the lw processes:  
   
    isi services -a lwsm enable
   
15. Run the following command to refresh the lwio process:
  
    isi_for_array /usr/likewise/bin/lwsm refresh lwio

16. Run the following command to display the PID values for the lw processes,
    and then compare the PID values displayed to the values noted in step 3
    of this procedure. The PID values should have changed between step 3
    and step 15 of this procedure.   
	
    isi_for_array "ps -ax | grep lw | grep -v grep" 

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

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 patch is being removed from a compliance mode cluster,
   log in using the compadmin account.

3. Manually shut down the lw processes: 

   isi services -a lwsm disable

4. Wait 30 seconds, and then run the following command to confirm that the
   lw processes are not running on any nodes: 

   isi_for_array -sI "ps -ax | grep lw | grep -v grep"   

   Nodes that are not running lw services will return the following when
   you run the ps command using the isi_for_array command. 
   
   node-1 exited with status 1
   node-3 exited with status 1
   
   Nodes that are running lw services will return information similar 
   to the following.
   
   NOTE: The PID values are listed in the table below, under the PID
   header.

   Node    PID               Time    Process name
   clus-2: 46234  ??  I      0:00.05 /usr/likewise/sbin/lwsmd --syslog
   --start-as-daemon
   clus-2: 46245  ??  I      0:00.18 lw-container lwreg (lwreg)
   clus-2: 46246  ??  S      0:00.04 lw-container netlogon (netlogon)
   clus-2: 46247  ??  S      0:00.12 lw-container lwio (lwio)
   clus-2: 46248  ??  S      0:00.41 lw-container lsass (lsass)
   clus-2: 46331  ??  I      0:00.03 /usr/likewise/bin/lwsm proxy nfs
   clus-2: 46339  ??  I      0:00.13 lw-container nfs (nfs)
   clus-2: 46350  ??  I      0:00.07 lw-container srvsvc (srvsvc)

5. If, after five minutes, the lw processes are still running, run the
   following command to stop the remaining lw processes, where <node#>
   is the number of the node on which the processes are still running,
   and <PID> is the PID of the lw process that needs to be stopped.  
 
   isi_for_array -n <node#> kill <PID>

6. Run the following command again to confirm that the remaining lw
   processes have stopped:

   isi_for_array -sI "ps -ax | grep lw | grep -v grep"   

   When all the lw processes have stopped running, proceed to the next
   step. Otherwise, repeat the previous step and this step until there
   are no more lw processes running. 

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

   isi pkg delete patch-164327

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

   isi pkg info

9. Confirm that patch-164327 does not appear in the list of installed
   packages.

10. Run the following command to enable the lw processes:  
   
    isi services -a lwsm enable
   
11. Run the following command to refresh the lwio process:
  
    isi_for_array /usr/likewise/bin/lwsm refresh lwio

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