To downgrade a patch on your TeamForge site using the YUM installer, you need to specify the TeamForge packages for the services enabled on the box and the list of CN-* packages that changed in that patch.
For the services enabled on the box, these are the
TeamForge rpms you need to specify in the patch downgrade command:
- app: teamforge-app, teamforge-etl, teamforge-scm
- etl: teamforge-etl, teamforge-scm
- scm: teamforge-scm
- database/datamart: teamforge-database
-
Stop TeamForge.
-
/etc/init.d/httpd stop
-
/etc/init.d/postgresql-9.0 stop
-
/etc/init.d/collabnet stop
-
Find the packages contained in the patch.
For example, let's say you ran this command:
- cat /opt/collabnet/teamforge/dist/conf/patches
and got this result:
118.1: CN-runtime,CN-jakarta-log4j,
118.2: CN-quartz,CN-runtime,
-
Run the downgrade command.
To downgrade from patch level 1 to patch level 0 in the above example, here's the command:
- yum downgrade teamforge teamforge-app teamforge-etl teamforge-scm teamforge-database TeamForge-installer CN-jakarta-log4j CN-runtime
To downgrade from patch level 2 to patch level 1 in the example, here's the command:
- yum downgrade teamforge teamforge-app teamforge-etl teamforge-scm teamforge-database TeamForge-installer CN-runtime CN-quartz
Note: During the downgrade, the site-options.conf file is automatically backed up into /opt/collabnet/teamforge-installer//6.1.1.0/conf.
-
Recreate the runtime environment.
- cd /opt/collabnet/teamforge-installer/6.1.1.0
- ./install.sh -r -n -V -I -d /opt/collabnet/teamforge
-
Start TeamForge.
-
/etc/init.d/httpd start
-
/etc/init.d/postgresql-9.0 start
-
/etc/init.d/collabnet start
-
Verify that the patch was reverted.
-
Log onto the site as a site administrator.
-
On the Admin tab, click System
Tools.
-
Click Build Information and observe which
patches are present.