CLI hang up at the very beginning

[vincent-pli]

See the below logs:

IBM Maximo Application Suite CLI Container v3.11.0

https://github.com/ibm-mas/ansible-devops
https://github.com/ibm-mas/ansible-airgap
https://github.com/ibm-mas/cli

Available commands:
  - mas install to launch a MAS install pipeline
  - mas provision-fyre to provision an OCP cluster on IBM DevIT Fyre (internal)
  - mas provision-roks to provision an OCP cluster on IBMCloud Red Hat OpenShift Service (ROKS)
  - mas provision-aws to provision an OCP cluster on AWS
  - mas provision-rosa to provision an OCP cluster on AWS Red Hat OpenShift Service (ROSA)
  - mas setup-registry to setup a private container registry on an OCP cluster
  - mas mirror-images to mirror container images required by mas to a private registry
  - mas configure-ocp-for-mirror to configure a cluster to use a private registry as a mirror

[ibmmas/cli:3.11.0]mascli$ mas install
IBM Maximo Application Suite Installer
Powered by https://github.com/ibm-mas/ansible-devops/ and https://tekton.dev/

Current Limitations
1. Support for airgap installation is limited to Core with IoT, Manage, Optimizer at present


1. Set Target OpenShift Cluster
  Server URL ..... > https://api.ocp410.cluster.local.com:6443
  Login Token  ... > sha256~51YsgDpzDogFDmu6Art8uOfHkWLbWXkTx0QM8rPsMzo

The process hang up at the very beginning, no error, no further logs
How could I figure out what exactly going on.

I have a centos 8 as bastion node and ocp with version 4.10.37
with nfs as the storage

[durera]

This is usually because the OCP server is using self-signed certificates ... we really need to add an --insecure-skip-tls-verify like is supported in the oc login command.

To workaround this for now .. run oc login xxx before running mas install ... you will likely be prompted to trust the certificate when you run the oc login command.

We'll use this issue to track the addition of --insecure-skip-tls-verify as an option ... and to make it better handle the case when someone doesn't add that option and tries to connect to a server that would need it.

[vincent-pli]

@durera you are exactly right, it works now, thanks

[durera]

This is fixed in PR #175 ... the CLI will now prompt whether the user wants to disable TLS verify to use clusters with self-signed certificates.