dmarkowski Respected Contributor.
Respected Contributor.
127 views

Upgrading CDF to 2019.02 error

Hello,

When I am trying to upgrade CDF from 2018.11.00104 to 2019.02 I get following error from jq parser I believe:

2019-06-21T09:23:58.773733813Z DEBUG exec_cmd # curl -k -s --connect-timeout 10 --noproxy 172.17.17.105 -X POST https://172.17.17.105:443/idm-service/v2.0/tokens --user transport_admin:cHqE5SwAomGizg== -H 'accept: application/json' -H 'content-type: application/json' -d '{ "passwordCredentials" : { "username" : "'core_admin'", "password" : "'dq3aYm5HamkLNw=='" }, "tenantName" : "Provider"}'|/opt/kubernetes/bin/jq --raw-output ".token?.id?"
2019-06-21T09:23:58.773733813Z DEBUG exec_msg : parse error: Invalid numeric literal at line 1, column 10
2019-06-21T09:23:58.773733813Z DEBUG exit_code: 4
2019-06-21T09:24:29.363529130+00:00 DEBUG Failed to get IDM token.. Wait for 5 seconds and retry: 1

Is any idea to repair it?

Regards, Darek

0 Likes
1 Reply
dmarkowski Respected Contributor.
Respected Contributor.

Update

After restarting CDF token from IdM can be extracted:

2019-06-23T07:33:23.998719769Z DEBUG exec_cmd # curl -k -s --connect-timeout 10 --noproxy 172.17.17.105 -X POST https://172.17.17.105:443/idm-service/v2.0/tokens --user transport_admin:cHqE5SwAomGizg== -H 'accept: application/json' -H 'content-type: application/json' -d '{ "passwordCredentials" : { "username" : "'core_admin'", "password" : "'dq3aYm5HamkLNw=='" }, "tenantName" : "Provider"}'|/opt/kubernetes/bin/jq --raw-output ".token?.id?"

2019-06-23T07:33:23.998719769Z DEBUG exec_msg : eyJ0eXAiOiJKV1MiLCJhbGciOiJIUzI1NiJ9.eyJzdWIiOiIyYzkwZGQ5MjY1ZDNkZjIyMDE2NWQzZGY1OWI1MDEwYSIsImlzcyI6IklkTSAxLjIyLjEiLCJjb20uaHBlLmlkbTp0cnVzdG9yIjpudWxsLCJleHAiOjE1NjEyNzcwMDUsImNvbS5ocC5jbG91ZDp0ZW5hbnQiOnsiaWQiOiIyYzkwZGQ5MjY1ZDNkZjIyMDE2NWQzZGY1NGVhMDBiMyIsIm5hbWUiOiJQcm92aWRlciIsImVuYWJsZWQiOnRydWV9LCJwcm4iOiJjb3JlX2FkbWluIiwiaWF0IjoxNTYxMjc1MjA1LCJqdGkiOiIxNWQ0ODI3OC1hM2RkLTQyZWEtYWFjYS1iNmZhZjRlM2I5NjEifQ.ddmzLxFf54iLPTRSBNK95wOlAtLJaR2CmlGz7dqIIn4

2019-06-23T07:33:23.998719769Z DEBUG exit_code: 0

 

But just in next action another error is produced:

 

2019-06-23T07:33:25.831920923Z DEBUG exec_cmd # curl -k -s --connect-timeout 10 --noproxy 172.17.17.13 -X GET https://172.17.17.13:8443/urest/v1.1/deployment?deploymentType=PRIMARY -H 'accept: application/json' -H 'content-type: application/json'  -H 'x-auth-token: 'eyJ0eXAiOiJKV1MiLCJhbGciOiJIUzI1NiJ9.eyJzdWIiOiIyYzkwZGQ5MjY1ZDNkZjIyMDE2NWQzZGY1OWI1MDEwYSIsImlzcyI6IklkTSAxLjIyLjEiLCJjb20uaHBlLmlkbTp0cnVzdG9yIjpudWxsLCJleHAiOjE1NjEyNzcwMDUsImNvbS5ocC5jbG91ZDp0ZW5hbnQiOnsiaWQiOiIyYzkwZGQ5MjY1ZDNkZjIyMDE2NWQzZGY1NGVhMDBiMyIsIm5hbWUiOiJQcm92aWRlciIsImVuYWJsZWQiOnRydWV9LCJwcm4iOiJjb3JlX2FkbWluIiwiaWF0IjoxNTYxMjc1MjA1LCJqdGkiOiIxNWQ0ODI3OC1hM2RkLTQyZWEtYWFjYS1iNmZhZjRlM2I5NjEifQ.ddmzLxFf54iLPTRSBNK95wOlAtLJaR2CmlGz7dqIIn4'' |/opt/kubernetes/bin/jq --raw-output ".?"

2019-06-23T07:33:25.831920923Z DEBUG exec_msg :

{

  "timestamp": 1561275460808,

  "status": 401,

  "error": "Unauthorized",

  "message": "Unauthorized",

  "path": "/urest/v1.1/deployment"

}

2019-06-23T07:33:25.831920923Z DEBUG exit_code: 0

2019-06-23T07:37:40.861612103+00:00 DEBUG DEPLOYMENT_UUID:

 

So I am stuck again.

 

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.