It's all about the answers!

Ask a question

Error during 502 migration finalization.

Mahari Hill (4861182230) | asked Mar 23 '15, 5:19 p.m.
edited Mar 26 '15, 12:40 p.m. by Patrick Remington (2013)
405-502 migration

We keep getting errors trying to upgrade to 502 from 405 during the rm/finalization steps (2 and 3). If #2 does not error out telling us the JTS and RM aren't friends, then step 3, which only choice is [E] for execute, errors by saying we failed to give the application ID and public URL during the step (it did not ask).

The instructions say we don't have to provide it, as it's done automatically.

Any advice? Can I fix this and rerun from step #3 without encountering the "rerunning RM upgrade will delete your RM data" defect?

Patrick Remington commented Mar 25 '15, 1:19 p.m.

Mahari, what information are you using to upgrade that has the steps 2 and 3 that you mentioned?

2 answers

permanent link
Mahari Hill (4861182230) | answered Mar 26 '15, 10:10 a.m.
We are thinking the documentation and script people must not be communicating. If you look at the 5.0.2 interactive upgrade guide, during the RM upgrade, it says

1) During the upgrade after the "(RM) finalizeApplicationMigration" step is complete, you will see the following message in the command window:

The following application was migrated: APPID000-0000-0000-0000-000000000000. To finalize the migration, on the Jazz Team Server that the application is registered with, run the finalizeApplicationMigration command with the "applicationId=APPID000-0000-0000-0000-000000000000" parameter.

You do not need to stop the script execution at this point to run the command that was described in the message. The next step in the upgrade script "(JTS) finalizeApplicationMigration" runs the command automatically.

OK, great. Then two paragraphs later it says:

During the upgrade, make a note of the RM application ID and public URL. At a later step when cleaning up the existing data from JTS, you will be prompted to enter the RM application ID and public URL. The application ID will also be logged in the repotools-rm_finalizeApplicationMigration.log file.

OK, that contradicted the previous statement. Either way, when you run rm_upgrade, step 2 and 3 only give the options of [E] to execute, skip or cancel..., so all of this should have been removed.

Patrick Remington commented Mar 26 '15, 2:05 p.m.

Hello, Mahari.  The author of the Interactive Update Guide is working with development to review it.

permanent link
Martha (Ruby) Andrews (3.0k44351) | answered Mar 26 '15, 1:10 p.m.
Hello Mahari,
If you are upgrading to 5.0.2, please make sure you have the latest iFix from Rational Support or Fix Central:

Without the iFix, running migration multiple times can cause loss of project areas. Here it the tech note for the issue:

Martha (Ruby) Andrews
Jazz Foundation L3 Development Team Lead

Your answer

Register or to post 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.