Here's a list of few noteworthy issues fixed in TeamForge 21.2 Update 1 and the instructions to apply TeamForge 21.2 Update 1.

Release Information

  • Released on: Feb 07, 2022
  • Update 1 Build: 21.2.222

Issues Fixed in TeamForge 21.2 Update 1 Release

  • Fixed an issue with Document Management—creating a new version of a document, regardless of the document’s current status, puts the document in DRAFT status, in both old and new Document Management UIs.

  • Fixed an installation/upgrade issue (teamforge provision fails) with TeamForge in a distributed setup (with separate database server that hosts application and binary databases).

  • Fixed the Open for SCM issue—the Open for SCM tracker status setting, if configured in the source project that was used to create a project template, is retained on all the projects that are created using the project template.

  • Fixed an issue (a query) that caused site downtime due to an out of memory error (OOME).

  • Fixed a webhook issue that prevented webhooks from being triggered for artifact updates.

  • Fixed a TeamForge SOAP call read timeout issue that prevented Gerrit from starting.

Apply TeamForge 21.2 Update 1

TeamForge 21.2 Update 1 is now available. Apply TeamForge 21.2 Update 1 on your site if you are on TeamForge 21.2.

TeamForge add-on packages can remain installed when you apply TeamForge 21.2 Update 1. No updates are required. However, you should verify the compatibility of Add-ons applied to your site as some may be more specific to your site.

The most common Add-ons and their TeamForge compatibility are published here: https://ctf.open.collab.net/sf/go/page1363.

If you have any questions regarding compatibility or updating a specific add-on, contact CollabNet Support.
  1. Stop TeamForge.
    teamforge stop
    
  2. Skip this step if your site has internet access. This step is to configure TeamForge 21.2 Update 1 installation repository on sites without Internet access.

    a. Contact the CollabNet Support to get the auxiliary installer package for TeamForge 21.2 Update 1 disconnected installation and save it in /tmp.

    • Red Hat Enterprise Linux/CentOS RHEL 8.4 64 bit RPM package: CTF-Disconnected-media-21.2.223-511.rhel8.x86_64.rpm
    • Red Hat Enterprise Linux/CentOS RHEL/CentOS 7.9 64 bit RPM package: CTF-Disconnected-media-21.2.223-511.rhel7.x86_64.rpm

    b. Back up the old repo file.

    For example:

       mv /etc/yum.repos.d/CTF-Disconnected-media-21.2.xxx.repo /etc/yum.repos.d/CTF-Disconnected-media-21.2.xxx.repo.cn_backup
    

    c. Unpack the 21.2 Update 1 disconnected installation package.

       rpm -Uvh <package-name>
    

    d. Verify your yum configuration files.

       yum list httpd
       yum list apr
    
  3. Configure your TeamForge installation repository. This step is to configure TeamForge 21.2 Update 1 installation repository on sites with Internet access.

    a. Remove the existing TeamForge repository package.

       yum erase collabnet-teamforge-repo-21.2-0.noarch
    

    b. Contact the CollabNet Support and download the TeamForge 21.2 Update 1 installation repository package to /tmp.

    c. Install the Teamforge 21.2 Update 1 installation repository package.

       yum install -y /tmp/collabnet-teamforge-repo-21.2-0.noarch.rpm
    

    d. Refresh your repository cache.

       yum clean all
    
  4. Install the TeamForge 21.2 Update 1.

    yum install teamforge
    

    The above command installs all the TeamForge updates available in the CollabNet yum repository for TeamForge 21.2.

  5. Check the /opt/collabnet/teamforge/var/scm/gerrit/gitroot directory. If it is empty, remove it manually.

    rm -rf gitroot
    
  6. Deploy services.

    teamforge provision
    
Tags for this page: ctf_21.2 release_notes