Virtual TapeServer 8.2 Release Notes

Resolved Issues and Enhancements | 13
 RPM warnings occurred during upgrade. When RPMs were installed on a system,
there were occasional conflicts where the new RPM had a configuration file, which was
different than the configuration file currently on the system. When this happened, the
configuration file on the system was renamed to xxx.rpmsave and the new configuration
file inside the RPM was delivered. This new configuration file may have been new/
different settings than the previous configuration. (TL-5313)
 vtspatch_* directory remained in /tmp after patch or IR delivery. Patch and IR
delivery processing left a scratch directory in /tmp named vtspatch_*, which is now
removed when patch or IR delivery is complete. (TL-7471)
 Software reinstall did not configure system as a software install did. If you
reinstalled VTS, the system was configured with a smaller OS file system than after a
new installation. A reinstallation also left eth1 unconfigured; an installation would
configure eth1 with the static IP address of 1.1.1.1. Now, reinstall behaves the same way
an install behaves. (TL-7055)
 Upgrade process did not ensure all processes were shut down. The upgrade may
not have shut down all processes before starting. This has been fixed. (TL-3196)
 Upgrade failed because TapeServer process could not be stopped. Processes can
be started intermittently by the web server (such as the System Status page) and cron
jobs. If one of these processes ran a process from /usr/local/tape/bin during an upgrade, the
upgrade could have failed. This has been fixed. (TL-5007)
 Upgrade and downgrade did not test for VTL activity before proceeding.
Upgrade and downgrade blindly stopped library emulations by unmounting the virtual
magazines. VTS now determines if the VTL is being used. (TL-5200)
 Upgrade or downgrade may have failed if web interface was refreshing. The
system status page displays information from the database, and it refreshes
automatically. If the page refreshed during an upgrade, the database update may have
failed because the database was opened by the refresh. This may have caused the upgrade
to fail. This may have also happened during a downgrade, and the system restore may
have failed to restore the system. The system would then be left in an unusable state. This
has been fixed. (TL-5203)
 Host reservation conflict on AS/400 caused upgrade to fail. When you attempted to
remove the reservation from AS/400, the tape would not vary off because TapeServer was
shutdown. If you then started TapeServer and then varied off the tape, a kernel panic
occurred. This has been fixed. (TL-6810)
 Error displayed when downgrading an 8.0 system that did not have a capacity
license. The following error was seen when downgrading a system from 8.0 that did not
have a capacity license:
mv: cannot stat '/usr/local/tape/etc/capacity_license': No such file
or directory
Though the error was ignorable, this has been fixed. (TL-6844)