DXOI installer fails with No content to map due to end-of-input error

Products

• DX Operational Intelligence

Issue/Introduction

Running a 5 node k8s cluster, 3 node ES on local disk with ONLY DOI application installation type.

After hitting enter button on my keyboard during the question of…
To check the NFS IOPS performance of the provided NFS server, execute the dxi-fio-docker script located in the tools/ directory.
Press <Enter> to continue this installation, or <ctrl-C> to exit.

Can see below error in the install.log

2024-04-09 02:10:18,541 TRACE - Prompt value null. User input = false

2024-04-09 02:10:18,559 TRACE - Running NfsIopsValidator

2024-04-09 02:10:18,561 TRACE - Prompt 3/59

2024-04-09 02:10:18,563 TRACE - Inner prompt 1/3, KubeClusterNamePrompt

2024-04-09 02:10:18,624 ERROR - [ ERROR ] For error details goto install.log file.No content to map due to end-of-input

 at [Source: (File); line: 1, column: 1]

2024-04-09 02:10:18,625 TRACE - [ERROR]

com.fasterxml.jackson.databind.exc.MismatchedInputException: No content to map due to end-of-input

 at [Source: (File); line: 1, column: 1]

at com.fasterxml.jackson.databind.exc.MismatchedInputException.from(MismatchedInputException.java:59)

at com.fasterxml.jackson.databind.ObjectMapper._initForReading(ObjectMapper.java:4916)

at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:4818)

at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:3637)

at io.fabric8.kubernetes.client.internal.KubeConfigUtils.parseConfig(KubeConfigUtils.java:43)

at com.ca.dxi.console.collector.prompt.KubeClusterNamePrompt.prompt(KubeClusterNamePrompt.java:28)

at com.ca.dxi.console.collector.ValidatedPrompt.execute(ValidatedPrompt.java:183)

at com.ca.dxi.console.collector.ValidatedPromptManager.setIndexes(ValidatedPromptManager.java:652)

at com.ca.dxi.console.collector.ValidatedPromptManager.executePrompts(ValidatedPromptManager.java:638)

at com.ca.dxi.console.collector.DxiDataCollector.process(DxiDataCollector.java:125)

at com.ca.dxi.console.collector.DataCollector.run(DataCollector.java:46)

at com.ca.dxi.console.ConsoleEntryPoint.run(ConsoleEntryPoint.java:43)

at org.springframework.boot.SpringApplication.callRunner(SpringApplication.java:762)

at org.springframework.boot.SpringApplication.callRunners(SpringApplication.java:752)

at org.springframework.boot.SpringApplication.run(SpringApplication.java:319)

at com.ca.dxi.DownloaderApplication.main(DownloaderApplication.java:32)

at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)

at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.base/java.lang.reflect.Method.invoke(Method.java:568)

at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:49)

at org.springframework.boot.loader.Launcher.launch(Launcher.java:95)

at org.springframework.boot.loader.Launcher.launch(Launcher.java:58)

at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:65)

 

 

 Mon Apr  8 22:10:18 EDT 2024 Command failed.

 

Environment

DXOI 23.3

Cause

In the error from install.log we can see fabric8 KubeConfigUtils failed to parse kubeconfig. 
Check if the kubeconfig is healthy (or it might be an issue in 3rd party tool fabric8). 

Original file is in $HOME/.kube/config and it is copied to <installer_dir>/config

Resolution

After restoring the kube config file the installer went through.