Super Contributor.. Levent Super Contributor..
Super Contributor..
424 views

IDM stays at 0/2 after upgrading CDF to 2019.02 (readiness probe fail)

Hello,

After upgrading the CDF to version 2019.02,  when checking kube-status   it seems idm deployment is not being up.   

from kube-status output:

Ekran AlıntısidmIDM.JPG

 

kubectl get deployments -n core    :  

idm 0/2 

 

kubectl get pods -n core:

Ekran AlıntısıNcore.JPG

kubectl describe pod idm-597756fd98-5bksp -n core :

...

..

Warning ....  .....               Readiness probe failed: HTTP probe failed with statuscode: 404

 

I can not login to both cdf administration and suite pages.

 

Any idea please?  

Thanks. 

Levent.

 

 

 

 

0 Likes
11 Replies
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Re: IDM stays at 0/2 after upgrading CDF to 2019.02 (readiness probe fail)

Hi Levent,

For this issue, I would suggest getting more information from idm logs, you can run the command as follows:

kubectl logs -f idm-xxxx -n core -c idm

Thanks,

Elva

0 Likes
Super Contributor.. Levent Super Contributor..
Super Contributor..

Re: IDM stays at 0/2 after upgrading CDF to 2019.02 (readiness probe fail)

hi,

there is an error in that log.  it says one or more configuration file is not provided.  

 

2019-06-11T09:04:30.623+0000 INFO [localhost-startStop-1] com.hp.sw.bto.ast.security.lwsso.conf.LWSSOConfigurationManager - com.hp.sw.bto.ast.security.lwsso.conf.LWSSOConfigurationManager was not initialized explicitly. Trying to initialize it implicitly from lwssofmconf.xml
2019-06-11T09:04:31.712+0000 INFO [localhost-startStop-1] com.hp.sw.bto.ast.security.lwsso.utils.StringEncrypter - StringEncrypter [ isUseEncryption = false] : One or any of configuration files is not provided ...
2019-06-11T09:04:31.819+0000 INFO [localhost-startStop-1] com.hp.sw.bto.ast.security.lwsso.conf.LWSSOConfigurationManager - Building of configuration completed in 1195 milliseconds.
2019-06-11T09:04:31.846000000+0000 SEVERE org.apache.catalina.core.StandardContext startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
2019-06-11T09:04:31.852000000+0000 SEVERE org.apache.catalina.core.StandardContext startInternal Context [/idm-service] startup failed due to previous errors

 

??? 

Before running upgrade-l and upgrade-u  I hadn't modified install.properties file in upgrade folder.   Should I had made it? 

 

0 Likes
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Re: IDM stays at 0/2 after upgrading CDF to 2019.02 (readiness probe fail)

Can you attach the log file with this command:  kubectl logs idm-xxxx -n core -c idm > idm.log, i am not sure whether the error message you posted is the cause or not.

Thanks,

Elva

0 Likes
Super Contributor.. Levent Super Contributor..
Super Contributor..

Re: IDM stays at 0/2 after upgrading CDF to 2019.02 (readiness probe fail)

Hi, 

ok.  I have attached that logs. I applied masking on private information like hostname, server name in the logs.  There are two pods in core namespace. Their logs are attached. 

Thanks in advance.

0 Likes
Highlighted
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Re: IDM stays at 0/2 after upgrading CDF to 2019.02 (readiness probe fail)

From the log(line 370 to 582), we can see that it caused by the migrate seeded data failed.  Maybe you need to check the seeded file: /opt/kubernetes/cfg/idm/seeded/com.microfocus.cdf__2019.02__Add_Update_User.json and check the "organizations"  table of CDF database, to see whether there is an organization with id: 2c90928f67d13d970167d13daddb00b3. if not, that's should be some kind of data issue, need to be fixed first. Thanks, Elva
0 Likes
Super Contributor.. Levent Super Contributor..
Super Contributor..

Re: IDM stays at 0/2 after upgrading CDF to 2019.02 (readiness probe fail)

Hi,

I have checked that organisation table in CDF database.   There is no line for that id.  There are two lines and their ids are different from this id.  Their display names are: "Service Management Automation"  and   in second line "IdMIntegration" .    There are no other lines in the table.  

 

0 Likes
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Re: IDM stays at 0/2 after upgrading CDF to 2019.02 (readiness probe fail)

what's the name of the 2 records? and can you attach the seeded file here?
0 Likes
Super Contributor.. Levent Super Contributor..
Super Contributor..

Re: IDM stays at 0/2 after upgrading CDF to 2019.02 (readiness probe fail)

Hi Elva,

I attched the seeded file. 

Names in organizations table lines are:

uuid: "2c9092866823a1d7016823a1f1a500b3"      name: "Provider"

uuid: "2c9092866823a1d7016823a1f24600d5"      name : "IdMIntegration"

Thanks for your helps

Levent. 

0 Likes
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Re: IDM stays at 0/2 after upgrading CDF to 2019.02 (readiness probe fail)

please run this command: kubectl get cm idm-conf-file -n core -o yaml

 

and check whether the content of com.microfocus.cdf__2019.02__Add_Update_User.json is as the same as the seeded file you attached.

Thanks,

Elva

0 Likes
Super Contributor.. Levent Super Contributor..
Super Contributor..

Re: IDM stays at 0/2 after upgrading CDF to 2019.02 (readiness probe fail)

Hi Elva,

Their contents are same until line 191 in notepad ++ .  Screenshot is below. In command output; some more lines until 201 which they are under the screen shot. 

 

compareIDMconfYamlandJson.png    

kind: ConfigMap
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"kind":"ConfigMap","apiVersion":"v1","metadata":{"name":"idm-conf-file","cr2__Add_Update_User.json":"[\n {\n \"operation\": \"ADD_OR_UPDATE\",\n \"typ\": \"Provider\"\n },\n \"attributes\": {\n \"name\": \"CLUSTER_ADMIN\"ription\": \"CLUSTER ADMIN ROLE\"\n },\n \"associations\": [\n {\n p\"\n },\n {\n \"name\": \"SUPER_IDM_ADMIN\",\n \"type\": _ADMIN\",\n \"type\": \"permission\"\n }\n ]\n },\n {\n \"oper\"names\": {\n \"organizationName\": \"Provider\"\n },\n \"attributes\"yName\": \"DEPLOYMENT ADMIN\",\n \"description\": \"DEPLOYMENT ADMIN ROLE\"\n: \"Administrators\",\n \"type\": \"group\"\n },\n {\n \"nn\"\n },\n {\n \"name\": \"MNG_ADMIN\",\n \"type\": \"permDD_OR_UPDATE\",\n \"type\":\"databaseUser\",\n \"names\":{\n \"organizaegration_admin\"\n },\n \"attributes\":{\n \"name\":\"integration_admine\": \"group\",\n \"name\": \"Administrators\"\n }\n ]\n },\n {\naseUser\",\n \"names\":{\n \"organizationName\":\"Provider\",\n \"dat:{\n \"name\":\"core_admin\"\n },\n \"associations\":[\n {\n \"\n }\n ]\n },\n {\n \"operation\":\"ADD_OR_UPDATE\",\n \"type\":me\":\"Provider\",\n \"databaseUserName\":\"itsma_admin\"\n },\n \"attrassociations\":[\n {\n \"type\": \"group\",\n \"name\": \"Admin\"ADD_OR_UPDATE\",\n \"type\":\"databaseUser\",\n \"names\":{\n \"organopsbridge_admin\"\n },\n \"attributes\":{\n \"name\":\"opsbridge_admin\\": \"group\",\n \"name\": \"Administrators\"\n }\n ]\n },\n {\n seUser\",\n \"names\":{\n \"organizationName\":\"Provider\",\n \"data\n \"name\":\"hcm_admin\"\n },\n \"associations\":[\n {\n \n }\n ]\n },\n {\n \"operation\":\"ADD_OR_UPDATE\",\n \"type\":\"d":\"Provider\",\n \"databaseUserName\":\"dca_admin\"\n },\n \"attributetions\":[\n {\n \"type\": \"group\",\n \"name\": \"AdministratoR_UPDATE\",\n \"type\":\"databaseUser\",\n \"names\":{\n \"organizationmin\"\n },\n \"attributes\":{\n \"name\":\"demo_admin\"\n },\n \" \"name\": \"Administrators\"\n }\n ]\n },\n {\n \"operation\":names\":{\n \"organizationName\":\"Provider\",\n \"databaseUserName\":\"\"nom_admin\"\n },\n \"associations\":[\n {\n \"type\": \"group\ }\n]\n"}}
creationTimestamp: "2019-06-10T07:48:55Z"
name: idm-conf-file
namespace: core
resourceVersion: "21887341"
selfLink: /api/v1/namespaces/core/configmaps/idm-conf-file
uid: 327130ed-8b54-11e9-a89f-00505699382a

 

Thanks for your interest and helps

 

Levent

 

 

 

 

0 Likes
Super Contributor.. Levent Super Contributor..
Super Contributor..

Re: IDM stays at 0/2 after upgrading CDF to 2019.02 (readiness probe fail)

Hi,

is there any abnormality about this difference?  

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.