Hello, I am having problems upgrading from 2.0 -> 2.0.3 from source using the install.sh script. The install script seems to become confused as to whether the installation is an initial one or a upgrade migration. There are two things that go wrong here (as far as I can tell):
1. There is a backup.tar file that is generated by the check_preexist() function of the build-functions.sh script. The existence of this file is used further along in the script to determine whether the installation is an initial one or a migration. The check_preexist function is called by run_checks, which in turn is called by build(). The problem comes a couple of steps later in the build() function when purge_backup() is called, the backup.tar file is deleted. This happens before the configure() function is called. The configure() function calls various functions in install-functions.sh that use backup.tar as a test. But this can seemingly never work since the backup.tar is always deleted by this point. 2. The create_database() function in install-functions.sh doesn't check for the existence of backup.sh, so it will always add zenoss with the default password. This throws off my upgrade since, I have the zenoss user having a non-default password from my earlier installtion. So I modified the installation scripts so that purge_backup was called before run_checks() in the build() function and so that create_database() checks to see if this is a migration upgrade before creating the zenoss database user and my migration went alot smoother. So am I the only one to experience this, or have others found a different workaround? Thanks. ------------------------ John -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=9055#9055 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
