Is this UCD v6.1.1.2 Defect? If yes can we get test fix for try? Pls let me know if IBM UCD Developer want to see our log, I dont want to up our log in public site. thanks.
plugin: IBM UrbanCode Deploy Resources, id: com.urbancode.air.plugin.uDeployResource, version: 66 plugin command: '/opt/ibm/ucd/agent/opt/groovy-1.8.8/bin/groovy' '-cp' '/opt/ibm/ucd/agent/var/plugins/com.urbancode.air.plugin.uDeployResource_66_7007046a5eb70138f97a834b6d06a8ee82621f886a9cfce8556483c5ad22e550/classes:/opt/ibm/ucd/agent/var/plugins/com.urbancode.air.plugin.uDeployResource_66_7007046a5eb70138f97a834b6d06a8ee82621f886a9cfce8556483c5ad22e550/lib/uDeployRestClient.jar:/opt/ibm/ucd/agent/var/plugins/com.urbancode.air.plugin.uDeployResource_66_7007046a5eb70138f97a834b6d06a8ee82621f886a9cfce8556483c5ad22e550/lib/jettison-1.1.jar' '/opt/ibm/ucd/agent/var/plugins/com.urbancode.air.plugin.uDeployResource_66_7007046a5eb70138f97a834b6d06a8ee82621f886a9cfce8556483c5ad22e550/create.groovy' '/opt/ibm/ucd/agent/var/temp/logs7511693666930390896/input.props' '/opt/ibm/ucd/agent/var/temp/logs7511693666930390896/output.props' working directory: /devops properties: PLUGIN_INPUT_PROPS=/opt/ibm/ucd/agent/var/temp/logs7511693666930390896/input.props PLUGIN_OUTPUT_PROPS=/opt/ibm/ucd/agent/var/temp/logs7511693666930390896/output.props agent= agentPool= name=WebSphereCell parent=/IBM Account/DST DevOps Development (Blue Zone)/DSTNextWeb/sbybz2143 /IBM Account/DST DevOps Development (Blue Zone)/DSTNextWeb/sbybz2143 role= environment: AGENT_HOME=/opt/ibm/ucd/agent AH_AUTH_TOKEN= AH_WEB_URL=https://sbybzxxx.cloud.dst.ibm.com:8443 AUTH_TOKEN= DS_AUTH_TOKEN= DS_SYSTEM_ENCODING=UTF-8 JAVA_OPTS=-Dfile.encoding=UTF-8 -Dconsole.encoding=UTF-8 PLUGIN_HOME=/opt/ibm/ucd/agent/var/plugins/com.urbancode.air.plugin.uDeployResource_66_7007046a5eb70138f97a834b6d06a8ee82621f886a9cfce8556483c5ad22e550 UD_DIALOGUE_ID=1af17b97-835c-4037-b53e-947ebde082dd WE_ACTIVITY_ID=072b9fb8-4f03-4b98-907a-bff95205ac95 ================================================================================ Caught: java.io.IOException: 400 Bad Request Error processing command: could not insert: [com.urbancode.security.ResourceForTeam] java.io.IOException: 400 Bad Request Error processing command: could not insert: [com.urbancode.security.ResourceForTeam] at com.urbancode.ud.client.UDRestClient.invokeMethod(UDRestClient.java:149) at com.urbancode.ud.client.ResourceClient.createResource(ResourceClient.java:102) at com.urbancode.ud.client.ResourceClient$createResource.call(Unknown Source) at com.urbancode.air.plugin.udeploy.resources.ResourceHelper.createResource(ResourceHelper.groovy:220) at com.urbancode.air.plugin.udeploy.resources.ResourceHelper$createResource.call(Unknown Source) at create.run(create.groovy:14)
Answer by Steve McGrew (3179) | Mar 05, 2015 at 12:24 PM
Hi Steve,
As you mentioned it would not be appropriate to post logs on a public site. Your best course of action is to raise a PMR and speak to support about this issue.
Answer by CLynch (49) | Mar 05, 2015 at 12:46 PM
I ran into this error when I copied a plugin step to my clipboard then renamed the process that step was from. I was seeing an error in the log file to the effect of "User xyz does not have read access to component "
To resolve this I went to Settings -> Authentication -> selected my Active directory realm -> tracked down my user name in the list -> then clicked Remove to the right of my user name.
Cleared my browser cache, closed my browser and re-opened the browser, logged back into UrbanCode deploy and it treated me like a new user. but I did have my step pallet back.
Hope this helps.
one thing to note is that our security is set up through authorization groups that are pulled from Active Directory. if your security is set up to use local accounts or user accounts directly. I'm not sure how urbancode deploy will respond to you deleting/re-adding your account.
Answer by JanVondracek (45) | Apr 03, 2015 at 04:49 AM
We had similar exception (org.hibernate.exception.ConstraintViolationException: could not insert: [com.urbancode.security.ResourceForTeam]) with Derby DB and UCDeploy 6.1.1.2. Patching to 6.1.1.3 seems to solve it.