Known issues while installing or upgrading Information Server to version 11.7.1.0 or later

During the Installation:

In many cases, you can avoid these issues by doing the Resolution action before the installation is started.

1. Error related to host name resolution
   [WARNING FileExisting-crictl]: crictl not found in system path
   See technote for details.
2. Pre-requirement warning during installation of the Microservices tier; Swap needs to be disabled.
3. 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.
4. 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 before 11.7.0.2.
5. 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.
6. Microservices tier system requirement checks are not validated when Installer GUI is not used. This issue is present in the original release of 11.7.1.0 but is not present in the 11.7.1.0 respin image.
7. Microservices tier system requirements check does not report a failure when the installed Docker version is not version 18.06.
8. On Windows, installation of the Microservices tier fails when passwordless SSH is used between the Information Server host and the Microservices tier master node. The installation fails even if a password is specified.
9. Suite Installer and Update Installer GUI panels intermittently exhibit rendering issues.
10. Upgrade the Microservices tier with the same user ID 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 installation location.
    Sometimes, when root is used to upgrade the Microservices tier by using Update Installer version 11.7.1.34 or earlier, you can 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."
11. Note: If you use Update Installer 11.7.1.34 or earlier, you can also encounter this issue while running as root since issue #10 requires sudo to be set up for root users too.
    If a non-root user is used to install or 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 can 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.
12. Installation of the Microservices tier can be done only by a user whose user ID and group ID are the same.
13. The early Requirements checker for installation of 11.7.1.2 on Red Hat Enterprise Linux 8 reports failures as follows, when required packages (for example, libXp, libXau, libXext, libX11, libX11-common, libxcb, libXmu) are missing.
           "FAILED: CDIPR2112I: Ensure that the required package libXp-1.0.0-15.1.el6.x86_64 is installed."
14. On some Windows systems, installation in GUI mode leads to an HTTP 500 error window in the web browser with a NumberFormatException.

Postinstallation issues:

1. The Microservices tier installation log, for example iiskubedeploy_2018_09_20_07_01_01.log, contains errors but the installation status is reported as Success.
2. Log in to Information Server launchpad applications by using the "Automatically log in" checkbox fails even when valid login credentials are provided. You might see the following in the WebSphere log: "The Response Message is: Error 500: java.lang.RuntimeException: Message is larger than modulus".
3. Microservices tier installation needs to be cleaned up, and reinstalled.
4. Uninstall of Information Server 11.7.1.0 on Windows does not clean up Db2. In C:\Windows\System32\drivers\etc, the Db2 ports are still listed. The Db2 services are still running and do not shut down.
5. 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.