How to upgrade Virtual Bugzilla Server from version 3.2.2 or earlier to version 3.4

Upgrade from VBS 3.2.2 to VBS 3.4 is not much different from other VBS upgrades. It boils down to:

  • Installing a blank new VBS server;
  • Extracting data and configuration from the old VBS server;
  • Putting the data and configuration into the new VBS;
  • Upgrading the data and checking the configuration.

  1. Install VBS 3.4 into a separate folder

    Do not overwrite old VBS!

  2. Start old and new Bugzilla servers

    Use VMWare Player or Workstation to open and start both old VBS and new VBS. When new VBS starts, write down its IP address, which is shown in Bugzilla URL. If needed, configure network on the new server.

  3. Login to the VBS 3.2.2 using 'bugzilla' account

    Use console, shown in the VMWare window, or a SSH client. The password is 'bugzilla', unless it has been changed.

  4. Make sure old VBS is not accessible

    If the old VBS is accessible while you are migrating data from it, someone may make changes which will be lost or will get in the way.

    The easiest way is to stop Apache web server:

    su - root -c "apache2 -k stop"
    when asked for a password, type 'root'

  5. Back up MySQL database

    Database dump contains all user data from Bugzilla. To create it, use mysqldump utility:

    mysqldump -uroot --add-drop-table --disable-keys bugs >/tmp/bugs.sql

  6. Create backup of local Bugzilla configuration

    Use the following commands:

    cd /home/bugzilla
    tar cf /tmp/bugzilla-data.tar --exclude=data/template localconfig data

  7. Create backup of your custom config files

    If you have customized Virtual Bugzilla Server somehow, create a tar archive with your custom configuration files. You will then unpack and apply them on the new server.

  8. Transfer backup files to the new VBS

    Use command:

    cd /tmp
    scp *.sql *.tar bugzilla@ IP_address_of_the_new_VBS:/tmp

    When asked about authenticity, enter yes.
    When asked for password, enter bugzilla — the default password for bugzilla account on the new VBS.

  9. Login to the new VBS

    Use root account with default password being root as well. You can login on console or use SSH client.

  10. Verify that backup files have been transferred

    cd /tmp
    ls -l *.sql *.tar

  11. Drop and create mysql database

    mysql -e 'drop database bugs'
    mysql -e 'create database bugs character set utf8'

  12. Import data into mysql database

    Command: mysql bugs <bugs.sql

  13. Unpack bugzilla configuration files

    su - bugzilla
    tar xf /tmp/bugzilla-data.tar

    It's probable that you will see warnings about time stamps — ignore them.

  14. (Optionally) Edit localconfig

    You probably need to change database access parameters in localconfig file: db_name, db_user and db_pass.

    Use joe localconfig to launch file editor and make arbitrary changes.

  15. Run checksetup.pl

    Run checksetup.pl, the Bugzilla's installation and upgrade uberscript.

    ./checksetup.pl

  16. Change urlbase parameter

    At last, you need to change the urlbase parameter in data/params file.

    If your old VBS is still using numerical URL (with IP address), you can try this:
    logout     (going back from "bugzilla" to "root" account)
    /vbs/update-bugzilla-urlbase.sh

    Otherwise, edit data/params manually.

  17. Move other configuration files that you have changed on the old VBS

    Other configuration files, like Apache and MySQL setup may be moved in the same way.

  18. Done!

    This is it. If there were no errors during the upgrade, you should now be able to access new Bugzilla with your old data and settings.

A few things to do after the upgrade

  • Check that e-mail sending works. If necessary, tweak Bugzilla configuration;
  • Back up your new VBS;
  • Do not delete your old VBS! That's your latest backup at this moment.

If something went wrong