Highlighted
SB_RRK Trusted Contributor.
Trusted Contributor.
1347 views

ITSMA-X - Unable to configure

Jump to solution

The Installation of CFD was fine though with some error in uploadsuiteimages-20171115064331.log, all the processes are running & CLI working fine.

When I start to configure ITSMA, it fails. We have checked all the recommended configuration, but unable to find any deviation. We first tried Demo Setup & later with separate Master & Worker Node but the same error appears in the logfile (deployer.log) – posted below

Can anyone help?

Regards

Rakesh


deployer.log

2017-11-15 08:23:50.261 ERROR 10 --- [http-nio-8081-exec-1] c.h.i.i.service.SSRestClient : ===GetIdmSigningKey with (url=https://master.mydomain.au:5443): Failed. Exception Message:: I/O error on GET request for "https://master.mydomain.au:5443/idm-service/api/system/configurations/items/idm.encryptedSigningKey": master.mydomain.au: Name or service not known; nested exception is java.net.UnknownHostException: master.mydomain.au: Name or service not known
2017-11-15 08:23:52.823 INFO 10 --- [http-nio-8081-exec-2] c.h.i.i.c.ItsmaInstallerController : Getting install status...
2017-11-15 08:23:52.825 INFO 10 --- [http-nio-8081-exec-2] c.h.i.i.c.ItsmaInstallerController : Installation Status: null
2017-11-15 08:23:57.815 INFO 10 --- [http-nio-8081-exec-3] c.h.i.i.c.ItsmaInstallerController : Getting install status...
2017-11-15 08:23:57.817 INFO 10 --- [http-nio-8081-exec-3] c.h.i.i.c.ItsmaInstallerController : Installation Status: null
2017-11-15 08:24:02.824 INFO 10 --- [http-nio-8081-exec-4] c.h.i.i.c.ItsmaInstallerController : Getting install status...
2017-11-15 08:24:02.827 INFO 10 --- [http-nio-8081-exec-4] c.h.i.i.c.ItsmaInstallerController : Installation Status: null
2017-11-15 08:24:07.812 INFO 10 --- [http-nio-8081-exec-5] c.h.i.i.c.ItsmaInstallerController : Getting install status...
2017-11-15 08:24:07.814 INFO 10 --- [http-nio-8081-exec-5] c.h.i.i.c.ItsmaInstallerController : Installation Status: null




uploadsuiteimages-20171115064331.log

[DEBUG] 2017-11-15 08:09:50 : Successfully got the suite-installer container id. Error response from daemon: Error processing tar file(exit status 1): lchown /upload-suite-image-progress.log: operation not permitted
[DEBUG] 2017-11-15 08:09:50 : Successfully copied file ./suite-install/offline_sync_logs/offline_sync_logs/upload-suite-image-progress.log to /pv_suite_install/ [DEBUG] 2017-11-15 08:09:50 : Successfully got the suite-installer container id.
Error response from daemon: Error processing tar file(exit status 1): lchown /2017.07: operation not permitted
Error response from daemon: Error processing tar file(exit status 1): lchown /i18n: operation not permitted
Error response from daemon: Error processing tar file(exit status 1): lchown /suitefeatures_message_de.json: operation not permitted
Error response from daemon: Error processing tar file(exit status 1): lchown /suitefeatures_message_en.json: operation not permitted
Error response from daemon: Error processing tar file(exit status 1): lchown /suitefeatures_message_es.json: operation not permitted
Error response from daemon: Error processing tar file(exit status 1): lchown /suitefeatures_message_fr.json: operation not permitted
Error response from daemon: Error processing tar file(exit status 1): lchown /suitefeatures_message.json: operation not permitted
Error response from daemon: Error processing tar file(exit status 1): lchown /itsma_suitefeatures.2017.07.json: operation not permitted
[DEBUG] 2017-11-15 08:09:54 : Successfully copied file ./suite-install/itsma/config/feature/ to /pv_suite_install/suite_feature/itsma/.
[INFO] 2017-11-15 08:09:54 : Upload suite feature data completed.
[INFO] 2017-11-15 08:09:54 : Upload-process successfully completed.
0 Likes
1 Solution

Accepted Solutions
Trusted Contributor.. dvanaswegen Trusted Contributor..
Trusted Contributor..

Re: ITSMA-X - Unable to configure

Jump to solution

Hi, I've seen this error before. Can you try the following steps please...

1. [all nodes] shutdown the CDF, using /opt/kubernetes/bin/kube-stop.sh
2. [all nodes] update /etc/hosts to include all node's ip + fqdn
3. [nfs node] copy above /etc/hosts contents or file to: /var/vols/itom/core/baseinfra-1.0/kube-dns-hosts/,  removing any line(s) with localhost.
4. [all nodes] restart the CDF; /opt/kubernetes/bin/kube-start.sh
5. [web] After the CDF is fully deployed, go back to the UI to run the suite install wizard.

Hope this helps!
If not, please post your install.properties and kube-status.sh output.

6 Replies
Micro Focus Expert
Micro Focus Expert

Re: ITSMA-X - Unable to configure

Jump to solution

Hello,

Is master.mydomain.au your actual host name? What is configured in the install.properties for the EXTERNAL_ACCESS_HOST?

Is it possible to share the install.properties file?

Best regards,

Brindusa

0 Likes
SB_RRK Trusted Contributor.
Trusted Contributor.

Re: ITSMA-X - Unable to configure

Jump to solution

I have changed the mydomain in error to be posted on the foru 🙂

Yes, hostnames are configured correction. I can post the install.properties files if that helps to solve the issue faster.

0 Likes
Trusted Contributor.. dvanaswegen Trusted Contributor..
Trusted Contributor..

Re: ITSMA-X - Unable to configure

Jump to solution

Hi, I've seen this error before. Can you try the following steps please...

1. [all nodes] shutdown the CDF, using /opt/kubernetes/bin/kube-stop.sh
2. [all nodes] update /etc/hosts to include all node's ip + fqdn
3. [nfs node] copy above /etc/hosts contents or file to: /var/vols/itom/core/baseinfra-1.0/kube-dns-hosts/,  removing any line(s) with localhost.
4. [all nodes] restart the CDF; /opt/kubernetes/bin/kube-start.sh
5. [web] After the CDF is fully deployed, go back to the UI to run the suite install wizard.

Hope this helps!
If not, please post your install.properties and kube-status.sh output.

SB_RRK Trusted Contributor.
Trusted Contributor.

Re: ITSMA-X - Unable to configure

Jump to solution

Thank you for your response. It seems I must have missed point 3.

Let me check & will update on the status.

0 Likes
SB_RRK Trusted Contributor.
Trusted Contributor.

Re: ITSMA-X - Unable to configure

Jump to solution

Point 3 helped but now getting new error while configuring uCMDB 😞

Will post details in new thread.

0 Likes
Trusted Contributor.. dvanaswegen Trusted Contributor..
Trusted Contributor..

Re: ITSMA-X - Unable to configure

Jump to solution

Great! Glad it worked. Seems like environment DNS was an issue, requiring that local workaround.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.