Failed upgrade to RM 5.0.2 in mergeLPAJTS step
We recently upgraded from CLM 5.0 to 5.0.2.
When we run the diagnostics for RM, we get:
Friend: the discovery resource at https://<servername>/admin/rootservices for "/admin" cannot be accessed:
The returned HTTP status was 404
The response body was
Not Found
The requested URL /admin/rootservices was not found on this server.
The output of the
./repotools-rm.sh -mergeLPAJTS lpaContextRoot=admin applicationContextRoot=rm oldJTSHome=/cm/IBM/JazzTeamServer_500GA//server/conf onlyRemoveFriend=true oldApplicationHome=/cm/IBM/JazzTeamServer_500GA//server/conf oldApplicationVersion=Previous Requirements Management application version
command did not show any errors.
'/admin' is still listed in the Friends list.
1. How do we fix this?
2. Is this a Defect because /admin was not removed by repotools-rm?
|
Accepted answer
Hello
Are you able to use LPA from https://<servername>/jts/lpa? If so, you can remove the Friends key manually:
The merge command can fail to remove the friend information if the oldJTSHome is set incorrectly, as was the case in this defect:
If the command fails to remove the friend, the log file should show this message OR a return code of "10":
Ruby Martha (Ruby) Andrews Jazz Foundation L3 Development Team Lead Jeff Birkner selected this answer as the correct answer
Comments
Jeff Birkner
commented Jun 22 '15, 2:37 p.m.
Hi,
We are able to see LPA in ../jts/lpa.
I read Defect 331570 and Task 335587. Thank you.
We did not get an error message when we ran:
$ sudo ./repotools-rm.sh -mergeLPAJTS lpaContextRoot=admin applicationContextRoot=rm oldJTSHome=/cm/IBM/JazzTeamServer_500GA/server/conf onlyRemoveFriend=true oldApplicationHome=/cm/IBM/JazzTeamServer_500GA/server/conf oldApplicationVersion=5.0
I believe the problem is that 'oldJTSHome=/cm/IBM/JazzTeamServer_500GA/server/conf' is on another server (a distributed system) and repotools could not find the /admin directory to be able to look up the Friends consumer key as mentioned in Task 335587, Description (#2).
I am disappointed that there was not an error message from repotools for this case and that the Interactive Upgrade Guide did not mention this for distributed systems.
- Jeff
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.