Skip to content

ZenHub Enterprise 3.2.1
Compare
Choose a tag to compare
@cwarje cwarje released this 30 Jul 22:44
· 65 commits to master since this release
v3.2.1
a9cd72b
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

These release notes are for ZenHub Enterprise for Virtual Machine and ZenHub Enterprise for Kubernetes.

  • For all users using ZenHub on github.com, please check out our new feature announcements on our product changelog.
  • For administrators planning upgrades, please refer to the section "Important Upgrade Instructions for Administrators".

IMPORTANT: ZenHub Enterprise 3.2 supports GitHub Enterprise versions: 2.22, 3.0, 3.1, and 3.2

What's new in ZenHub Enterprise 3.2.1

Features

  • None

Security Fixes

  • None

Bug Fixes

  • Fixed race condition that would occur during a restore from database backups, which also affected upgrades from ZHE 3.1 to ZHE 3.2.0
  • Upgrade bundle for VM now performs more preliminary checks to ensure the environment meets upgrade requirements

Changes

  • Increased timeout duration for backups and restores to better handle a large amount of data
  • URL redirect setup to point IP requests to the hostname

Known Issues

  • Too many authentication failures may be reported when attempting to SSH into the VM, which can be caused by multiple SSH keys loaded in the connecting workstation's SSH agent. A workaround is present in the documentation.
  • File uploads in the web application (not extension) are limited to 1MB in size.
  • On more recent versions of GitHub Enterprise, when viewing a GitHub issue from the GitHub issues list the ZenHub extension may require a page refresh to display ZenHub props such as Estimate and Epic

VM Embedded Component Versions

Component Version
Ubuntu 20.04.2
K3s v1.20.8+k3s1
Kubernetes v1.20.8
Kustomize v3.9.4
Fluentd v1.6-debian-1
Postgresql 11.12.0
MongoDB 4.4.6
RabbitMQ 3.8
Redis 6.2
PgBouncer 1.15.0

Important Upgrade Instructions for Administrators

ZenHub Enterprise for Virtual Machine

⚠️ NOTE: Specifically for the upgrade from ZHE 3.1 -> ZHE 3.2.1, the regular rollback steps cannot be used. Please perform a machine level snapshot prior to upgrading to use as a backup in case you need to revert back to ZHE 3.1 for any reason.

  • For users currently running ZenHub Enterprise 2.44, you must first migrate to 3.1.1 prior to upgrading to 3.2.1
  • For users currently running ZenHub Enterprise 3.1.0 or 3.1.1, look for an email from our team which will include a download link for the 3.2.1 upgrade package. The upgrade process is detailed in our documentation.

If you have previously performed a restore while using ZenHub Enterprise 3.1 (via zhe-config --restore), we have released a patch file that must be applied before performing the upgrade to ZenHub Enterprise 3.2.1. Follow the steps below to apply and then upgrade (we recommend all customers perform steps 1 and 2 before the upgrade):

  1. Download the patch to your VM
  2. Run the patch via bash zhe_31x_restore_patch.run
  3. Perform a restore from a snapshot using zhe-config --restore
  4. Take a machine level backup of the VM
  5. Run the 3.2.1 upgrade as per our documentation

ZenHub Enterprise for Kubernetes

  • Upgrading from 3.2.0 -> 3.2.1 is possible, but not necessary. No changes have been made to the app, as this release only contains fixes to the upgrade path for ZenHub for VM. If you would still like to upgrade your ZenHub cluster from 3.2.0 to 3.2.1, you can follow the regular application upgrade steps.
Assets 2