Known issues while installing an Information Server 11.7.1.0 Service Pack or Fix Pack

During the Install:

In many cases, you can avoid these issues by doing the Resolution action prior to starting the install.

1. Error related to host name resolution
   [WARNING FileExisting-crictl]: crictl not found in system path
   See Technote for details.
2. Upgrade failures due to limited free disk space reported as DiskPressure:
   Sep 27 14:57:36 CO9020091182 kubelet: W0927 14:57:36.204160   13593 eviction_manager.go:142] Failed to admit pod kube-proxy-djsx3_kube-system(e81c5638-c254-11e8-b444-005056941056) - node has conditions: [DiskPressure]
   See Technote for details.
3. Information Server Enterprise Search (ISES) fails because the Docker service encountered problems during startup. See Technote for details. This issue is also applicable to releases prior to 11.7.0.2.
4. After ISES 11.7.1.0 installation, or upgrade to 11.7.1.0, some pods are in CrashLoopBackOff state and examining the logs of such pods indicates an error
   "Unable to obtain connection from database (jdbc:db2://iis-db:50000/xmeta) for user 'xmeta': [jcc][t4][10380][11951][4.23.42] Required property "iis-db" is unknown host. ERRORCODE=-4222, SQLSTATE=08001"
   See Technote for details.
5. Suite Installer and Update Installer GUI panels intermittently exhibit rendering issues.
6. The Microservices tier pre-requirements checker does not report inadequate free disk space.
7. Upgrades of the Microservices tier should be run by the same user that initially installed the Microservices tier.
   The Update Installer checks that the specified user has root privileges and access rights for Kubernetes and the Microservices tier install location.
   Sometimes, when root is used to upgrade the Microservices tier using Update Installer version 11.7.1.34 or earlier, you may get the following error even if those conditions are met:
         "Since the root user was used to install the Microservices tier, the current user (root) must have root privileges to patch the installation.".
8. Note: If you use Update Installer 11.7.1.34 or earlier, you may also encounter this issue while running as root due to issue #7 above that requires sudo to be setup for root users too.
   If a non-root user is used to install/upgrade the Microservices tier, in the /etc/sudoers file, there is a "requiretty" setting that can cause the following messages to appear in the kube deployment log:
                 a. A "sudo: sorry, you must have a tty to run sudo" message when sudo is invoked.
                 b. While "yum install zip" is running, you may get a message
                           "ERROR: With yum install of zip. You can try to install requirement manually"
                      This error can appear even if zip is installed as needed.
9. If the Watson Knowledge Catalog Professional plan was installed during the install of Information Server 11.7.1.0 then while installing an Information Server 11.7.1.0 Service Pack, the Update Installer GUI panel will display a patch validation error. See Technote for details.
10. If the microservices tier installation fails with below mentioned error when installing IIS and microservices from Windows server with SSH passwordless authentication mode.
    "ssh: Could not resolve hostname C Name or service not known"
11. A NumberFormatException is intermittently reported in a number of install scenarios, using various browsers and browser versions:
    java.lang.NumberFormatException: For input string: "50.400001525878906"
    at java.lang.NumberFormatException.forInputString(NumberFormatException.java:76)
12. Applying 11.7.1.1 to an installation that has a Microservices tier, and uses WebSphere Application Server Network deployment (WAS ND) intermittently fails after upgrade of the Microservices tier indicates "Success".
     
    The install log contains the following error messages:
    020-05-14T01:37:37.845, INFO: CDIIN2951I: Action: PkgScript File: /opt/IBM/InformationServer/UGDockerDeployment/bin/LaunchUGDeployment.sh lin-test0716-int.fyre.ibm.com root false false false 1 ... Success
    2020-05-14T01:37:37.845, INFO: Stopping the Application Server
    .....
    Server stop request issued. Waiting for stop status.
    ADMU3111E: Server stop requested but failed to complete.
    ADMU0111E: Program exiting with error:
    com.ibm.websphere.management.exception.AdminException: ADMU3060E:
    Timed out waiting for server shutdown.
    ....
    2020-05-14T01:58:59.846, SEVERE: com.ibm.is.install.update.installer.Updater^M
    java.lang.Exception: CDIIN4559E: Could not stop WebSphere Application Server profile: /opt/IBM/WebSphere/AppServer/profiles/InfoSphere.
     
13. Applying 11.7.1.1 to an installation that has a Microservices tier, and uses WebSphere Application Server Network deployment (WAS ND) intermittently fails during upgrade of the Microservices tier.
     
    The install log contains the following error messages:
    RUNNING HANDLER [com/ibm/ugi/iis/iis-external : Ensure IIS classic launchpad is accessible] ***
    Wednesday 13 May 2020 02:32:57 -0700 (0:00:06.749) 0:46:21.769 *********
    FAILED - RETRYING: Ensure IIS classic launchpad is accessible (10 retries left).
    .....
    fatal: [deployment_coordinator]: FAILED! => {"attempts": 10, "changed": false, "content": "", "elapsed": 30, "msg": "Status code was -1 and not [200]: Connection failure: ('The read operation timed out',)",
    "redirected": false, "status": -1, "url": "https://11711-msfs-int.fyre.ibm.com/ibm/iis/launchpad/"}
    ....
    com/ibm/ugi/iis/iis-external : Ensure IIS classic launchpad is accessible - 386.73s
    Load all container images --------------------------------------------- 258.11s
    com/ibm/ugi/kubeplatform/kubernetes : Wait for Cluster DNS service to become available - 191.92s
14. In case of Microservices Tier deployment (install/upgrade) NO special character is supported for IIS users and passwords like isadmin, xmeta, dsadm, Kafka SASL, Solr etc.

15. Applying 11.7.1.1 to an installation that has a Microservices tier, and uses WebSphere liberty (LWAS) intermittently fails after install/upgrade of the Microservices tier indicates "Success".

    Exception:
    Either The install log contains the following error messages:
    server stop executed successfully.
    Its failed to start the server.its taking more than 60 secs to start the LWAS server.

    InstallAction (_id = start.lwas.on.windows.ug, _installUnitModelId = UGDockerDeploymentServices)
    _action = START
    _serviceName = InfoSvr
    _seconds = 60
    _numberOfRetries = 1
    )
    OR Below exception
    C:\Users\Administrator\AppData\Local\Temp\2\ibm_is_temp.2020.06.22.09.51.06\scripts\service.js start InfoSvr 60 1, env = null, workingDir =null
    Jun 22, 2020 1:13:29 PM com.ibm.is.install.core.CommonProcess
    INFO: Exit Code: 1, Info: action = start
    serviceName = InfoSvr
    Service state for InfoSvr after attempt number 1 is Start Pending
    Unable to start service InfoSvr, service state = Start Pending
    Jun 22, 2020 1:13:29 PM com.ibm.is.install.core.SuiteLogger logError
    SEVERE: com.ibm.is.install.engine.runtime.InstallEngine
    com.ibm.is.install.exception.ActionException: CDIIN5123E: WindowsServiceStopStartAction failed: the process returned error code 1.:CDIIN5106I: Details:
    WindowsServiceStopStartAction (CDIIN5106I: Details:
    InstallAction (_id = start.lwas.on.windows.ug, _installUnitModelId = UGDockerDeploymentServices)
    _action = START
    _serviceName = InfoSvr
    _seconds = 60
    _numberOfRetries = 1
    )

16. Intermittent Weave network issue while upgrading  11.7.1.0  or 11.7.1.1  installations on RHEL 7 to version 11.7.1.2 on RHEL 8 may result in multiple pods getting into an error state.
    a. Locate Weave pod name in the output of
               kubectl get pods -n kube-system
    b. Display Weave container logs
        kubectl logs -n kube-system <weave_pod_name> -c weave
    c. The problem is present if the logs contain the message:
              ipset v7.2: Set cannot be destroyed: it is in use by a kernel component

Post-installation issues:

1. Login to Information Server launchpad applications using the "Automatically log in" checkbox fails even when valid login credentials are provided. You may see the following in the WebSphere log: "The Response Message is: Error 500: java.lang.RuntimeException: Message is larger than modulus".
2. Microservices tier installation needs to be cleaned up, and re-installed.
3. Uninstall of Information Server 11.7.1.0 on Windows does not cleanup Db2. In C:\Windows\System32\drivers\etc the Db2 ports are still listed. The Db2 services are still running and do not shut down.
4. Clicking the Administration console and Metadata Asset manager icons on the Information Server microservices launchpad does not go through the HTTP server, and is redirected to Node 1 of the WebSphere Network Deployment cluster.
5. From the InfoSphere Information Server Launchpad, trying to launch Information Governance Catalog(IGC) via the IGC icon returns the error:

   Error 404: com.ibm.ws.webcontainer.servlet.exception.NoTargetForURIException: No target servlet configured for uri: /ibm/iis/igc
   In the Websphere Application Server(WAS) Console, the following applications are 'stopped':
        igc-web, igc-rest, igc-rest-explorer

6. Unable to login to the Information Server Administration (web) console after installing 11.7.1 Fix Pack 1.