Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE
sdr_dlo Absent Member.
Absent Member.
1406 views

ALM Synchonizer with JIRA - Error Integrity check - FAILED_TO_READ_EP_SCHEMA

Hi,

We want synchronize ALM with JIRA but we are not able to retrieve schema from JIRA during creation link process.

There is an error message indicating : the value "Nouvelle fonctionnalité" don't exist for the field "issuetype"

("Nouvelle fonctionnalité" is same as "Improvement")

The exact message display is :

ERROR #1- server.link.FAILED_TO_READ_EP_SCHEMA : Failed to read endpoint schema. Error: server.link.FAILED_TO_READ_EP_SCHEMA : Failed to read endpoint schema. Error: server.RemoteExecService.UNHANDLED_EXCEPTION : Unknown exception type is caught: com.hp.qc.synchronizer.adapters.exceptions.AdapterException: adapter.GENERAL_FAILURE...
ERROR #2- server.link.FAILED_TO_READ_EP_SCHEMA : Failed to read endpoint schema. Error: server.RemoteExecService.UNHANDLED_EXCEPTION : Unknown exception type is caught: com.hp.qc.synchronizer.adapters.exceptions.AdapterException: adapter.GENERAL_FAILURE..
ERROR #3- server.RemoteExecService.UNHANDLED_EXCEPTION : Unknown exception type is caught: com.hp.qc.synchronizer.adapters.exceptions.AdapterException: adapter.GENERAL_FAILURE.
ERROR #4- adapter.GENERAL_FAILURE
ERROR #5- com.mercury.qc.gossip.adapters.jira.exception.RestClientException: Failed : HTTP error code : 400 'Bad Request' with message: {"errorMessages":["La valeur 'Nouvelle fonctionnalité' n'existe pas pour le champ 'issuetype'."],"errors":{}}
ERROR #6- Failed : HTTP error code : 400 'Bad Request' with message: {"errorMessages":["La valeur 'Nouvelle fonctionnalité' n'existe pas pour le champ 'issuetype'."],"errors":{}}

Our JIRA level is V6.3.9

our ALM version is 11.00

There is no problem with ALM Check

Thanks for your replies

 

0 Likes
3 Replies
ameyjo Outstanding Contributor.
Outstanding Contributor.

Re: ALM Synchonizer with JIRA - Error Integrity check - FAILED_TO_READ_EP_SCHEMA

Please check the Jira Meta data to find out a if there is an issue with the entity types.  :

Error: errorMessages":["La valeur 'Nouvelle fonctionnalité' n'existe pas pour le champ 'issuetype'."],"

Seems the issue type does not exist,  Check the Jira Metadata and look for the type:

1.       http://<JIRA_SERVER_NAME_WITH_PORT>/rest/api/2/issue/createmeta?projectKeys=<JIRA_PROJECT_KEY>&expand=projects.issuetypes.fields

2.      http://<JIRA_SERVER_NAME_WITH_PORT>/rest/api/2/issue/<JIRA_SOME_ISSUE_KEY>?expand=schema

3.       http://<JIRA_SERVER_NAME_WITH_PORT>/rest/api/2/issue/<JIRA_SOME_ISSUE_KEY>/editmeta

4.       http://<JIRA_SERVER_NAME_WITH_PORT>/rest/api/2/field

 Where <JIRA_SERVER_NAME_WITH_PORT> is a URL of Jira server used.

<JIRA_PROJECT_KEY> is a Jira key for the project,

<JIRA_SOME_ISSUE_KEY> is a Jira key for any existing issue, for example it could be DEMO-00 for the issue in the project DEMO.

the question is why does ALM Synchronizer refer this non existing issue type? I presume that in the time when the link was created there was a type with this name. After that JIRA configuration was probably changed and the type is no longer available.

Did you try to create a new link again when issue type 'Nouvelle fonctionnalité' is present? This link should work as long as the JIRA issue type name stays intact.

If all is fine please login to Jira project in any browser, then execute these above requests and send the results to support through a new suppor ticket.

Cordially

 

"HP Support
If you find this or any post resolves your issue, please be sure to mark it as an accepted solution"
sdr_dlo Absent Member.
Absent Member.

Re: ALM Synchonizer with JIRA - Error Integrity check - FAILED_TO_READ_EP_SCHEMA

Thanks for your reply Ameyo

The link was created yesterday and the jira configuration was not change after this creation.

I use your links below but it seems that it doesn't work for the  third link

- First link : it seems tahat issuetypes exist in my project :

{"expand":"projects","projects":[
{"self":"http://<JIRA_SERVER_NAME_WITH_PORT>/rest/api/2/project/22504",
"id":"22504",
"key":"POCMAFUN",
"name":"POC SQUASH MAAF - Projet 1",
"avatarUrls":
  {"48x48":"http://<JIRA_SERVER_NAME_WITH_PORT>/secure/projectavatar?pid=22504&avatarId=10011",
  "24x24":"http://<JIRA_SERVER_NAME_WITH_PORT>/secure/projectavatar?size=small&pid=22504&avatarId=10011",
  "16x16":"http://<JIRA_SERVER_NAME_WITH_PORT>/secure/projectavatar?size=xsmall&pid=22504&avatarId=10011",
  "32x32":"http://<JIRA_SERVER_NAME_WITH_PORT>/secure/projectavatar?size=medium&pid=22504&avatarId=10011"},
"issuetypes":[
  {"self":"http://<JIRA_SERVER_NAME_WITH_PORT>/rest/api/2/issuetype/1","id":"1","description":"Problème altérant ou     compromettant les fonctions du produit.","iconUrl":"http://<JIRA_SERVER_NAME_WITH_PORT>/images/icons/issuetypes/bug.png","name":"Bogue","subtask":false},
  {"self":"http://<JIRA_SERVER_NAME_WITH_PORT>/rest/api/2/issuetype/4","id":"4","description":"Amélioration ou perfectionnement apporté à une fonction ou tâche
existante.","iconUrl":"http://<JIRA_SERVER_NAME_WITH_PORT>/images/icons/issuetypes/improvement.png","name":"Amélioration","subtask":false},
  {"self":"http://<JIRA_SERVER_NAME_WITH_PORT>/rest/api/2/issuetype/2","id":"2","description":"Nouvelle fonctionnalité du produit, qui doit encore être
développée.","iconUrl":"http://<JIRA_SERVER_NAME_WITH_PORT>/images/icons/issuetypes/newfeature.png","name":"Nouvelle fonctionnalité","subtask":false} ]}]}

 - Second link :  I extract some lines from the webpage and the result is :

[],"reporter":{"self":"http://<JIRA_SERVER_NAME_WITH_PORT>/rest/api/2/user?username=M003512","name":"M003512","emailAddress":"DisabledAccount_M003512@XXXXXXXXX.XX",
"avatarUrls":
{"48x48":"http://<JIRA_SERVER_NAME_WITH_PORT>/secure/useravatar?avatarId=10122",
"24x24":"http://<JIRA_SERVER_NAME_WITH_PORT>/secure/useravatar?size=small&avatarId=10122",
"16x16":"http://<JIRA_SERVER_NAME_WITH_PORT>/secure/useravatar?size=xsmall&avatarId=10122",
"32x32":"http://<JIRA_SERVER_NAME_WITH_PORT>/secure/useravatar?size=medium&avatarId=10122"},
"displayName":"XXXXXXX","active":false},"aggregateprogress":{"progress":0,"total":0},"customfield_16701":null,"customfield_16700":null,"customfield_16939":null,
"progress":{"progress":0,"total":0},"votes":{"self":"http://<JIRA_SERVER_NAME_WITH_PORT>/rest/api/2/issue/POCMAFUN-1/votes","votes":0,"hasVoted":false},
"worklog":{"startAt":0,"maxResults":20,"total":0,"worklogs":[]},
"issuetype":{"self":"http://<JIRA_SERVER_NAME_WITH_PORT>/rest/api/2/issuetype/1","id":"1","description":"Problème altérant ou compromettant les fonctions du produit.",
"iconUrl":"http://<JIRA_SERVER_NAME_WITH_PORT>/images/icons/issuetypes/bug.png","name":"Bogue","subtask":false},
"timespent":null,"customfield_15203":null,"project":{"self":"http://<JIRA_SERVER_NAME_WITH_PORT>/rest/api/2/project/22504","id":"22504","key":"POCMAFUN",
"name":"POC SQUASH MAAF - Projet 1","avatarUrls":
{"48x48":"http://<JIRA_SERVER_NAME_WITH_PORT>/secure/projectavatar?pid=22504&avatarId=10011",
"24x24":"http://<JIRA_SERVER_NAME_WITH_PORT>/secure/projectavatar?size=small&pid=22504&avatarId=10011",
"16x16":"http://<JIRA_SERVER_NAME_WITH_PORT>/secure/projectavatar?size=xsmall&pid=22504&avatarId=10011",
"32x32":"http://<JIRA_SERVER_NAME_WITH_PORT>/secure/projectavatar?size=medium&pid=22504&avatarId=10011"},"projectCategory":{"sel.............

- Third link don't work

- Fourth link : yhere is no référence to issuetype in the results.

have you an idea ?

best regards

0 Likes
ameyjo Outstanding Contributor.
Outstanding Contributor.

Re: ALM Synchonizer with JIRA - Error Integrity check - FAILED_TO_READ_EP_SCHEMA

Please open new support case, think it is the right step to do if you still have this problem.

Cordially

"HP Support
If you find this or any post resolves your issue, please be sure to mark it as an accepted solution"
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.