Jazz Build Engine fails to connect to RTC after upgrade to 6.0.5
We recently upgraded an RTC 4 instance to 5, and afterwards to 6.
When testing the Jazz Build Engine, by starting it with the same arguments used in version 4, we get the following error:
An error response was received from the Jazz Team Server. Status=400. Message: CRJAZ1848E To perform the "Control The Build Lifecycle" operation, the user (userid="ADMIN") must have one of the following licenses that are installed on the server: Rational Team Concert.Developer-Floating, Rational solution for Collaborative Lifecycle Management.Practitioner. The server administrator can assign licenses.. The error description is: An error response was received from the Jazz Team Server. Status=400. Message: CRJAZ1848E To perform the "Control The Build Lifecycle" operation, the user (userid="ADMIN") must have one of the following licenses that are installed on the server: Rational Team Concert.Developer-Floating, Rational solution for Collaborative Lifecycle Management.Practitioner. The server administrator can assign licenses.
The problem is the build engine is not started with the ADMIN user id specified in the error. We start it a user created specifically for builds, with the following license assigned: Rational Team Concert - Build System
The command line used to start the jbe is:
./jbe -repository https://rtc-hostname:9443/ccm -userId Builduser -passwordFile /path/to/passwdfile -engineId Build_4
JBE version is 6.0.5, JTS and CCM is 6.0.5 as well.
All servers involved are running on RHEL 7.4
Any ideas on what the problem would be?
2 answers
I would suggest that the licenses for the actual user are verified as assigned. Lack of license has been reported this way for a while..
There is something very wrong and confusing. Since you don't provide any thing in form of how you start the JBE there is no way we can tell.
The user ADMIN is fishy
The message complains you talk to the Jazz Team Server
The build user only needs the build license you mention BUT that license must be available.
As long as you are not willing to provide more, I must assume there is something wrong with the call you make.
I would suggest to talk to support. They don't publish your data. Otherwise obfuscate the sensible data and share your call and other data such as OS and JBE version.
Comments
