PerfSONAR v1.0 Fixed Bugs
From GEANT2-JRA1 Wiki
Contents |
[edit]
RC1 Bugs
| Bug #: | 26 |
| Reporter: | Stijn Verstichel |
| Issue: | The 'org.perfsonar.*' structure is not found when attempting to run the client tests post installation. |
| Fix: | During replication phase it was discovered that the CLASSPATH as reported was ordered in such a way that the perfSONAR classes where not loaded. After re-ordering this error was replaced by another related to a missing class yet again. After additional wrangling the proper jars in the proper order produced the expected result. |
| RC2 Change: | It is a little far fetched to expect all CLASSPATHs will be set up properly all the time. As such, any script that utilizes java will be provided with a known to work CLASSPATH. Proper instructions will be displayed during the installation procedure on the proper jars and the order they must be listed when constructing the variable on the local machine. |
| Bug #: | 27 |
| Reporter: | Vedrin Jeliazkov |
| Issue: | Warning messages 'log4j:WARN ...' are displayed when interacting with the Admin program for tomcat/axis. |
| Fix: | Also a CLASSPATH issue, a key jar was missing that included the necessary functionality. |
| RC2 Change: | The same change as was implemented for Bug #26. |
| Bug #: | 31 |
| Reporter: | Jason Zurawski |
| Issue: | NMWG parsing classes were performing slow. |
| Fix: |
Several portions of the NMWG (meant to aid in testing) were included into the various release stages. These sections included a very expensive file write using the toXML() procedures as well as another very expensive file write into a DOM format. These were commented. |
| RC2 Change: | Code was updated, and the release jars were re-built. |
| Bug #: | Through E-Mail |
| Reporter: | Vedrin Jeliazkov |
| Issue: | Not enough ant targets to test the release, such as: ant ls-run-client-query, ant xmldb-init-rrdma, ant xmldb-list-rrdma, and ant xmldb-resource-remove-rrdma. This actually brings another important point to light, the fact that there are 2 different ways to do the rrdma: one featuring eXist, and one that doesn't. |
| Fix: | More tests should be added to the client section to match what is available in the ant targets. Currently only the rrdma that does not use eXist is configurable. Some minor changes to the install procedure can allow for the switching between a static xml file and the XML db. |
| RC2 Change: | Additional functionality has been added to the client scripts. The ability to opt in or out of the eXist db for the rrdma will be added into the configuration process. The eXist deployment for both the LS and the MA is automatic. |
[edit]
RC2 Bugs
| Bug #: | 32 |
| Reporter: | Vedrin Jeliazkov |
| Issue: | Log file directory's variable '${logDir}' is not initialized in 'log.sh'. Additionally, it was suggested that the log file size become variable. |
| Fix: | Initialize the variable, ensure that the log directory is being set, and logs are being entered there instead of in the root of the filesystem. |
| RC3 Change: | The '${logDir}' was actually initialized, but the scope of use was a little off. Instead of being printed as '${logDir}' in the echo statement, it should have been '\${logDir}'; the logDir was declared local to the log conf file, not to the shell script that created it.
Additionally the size of the log files is variable now as well. This issue may want to revisited as a group though. In my opinion a default value is acceptable here, and the interested could modify this on their own if it too large or small. We may not want to pester the user with too many questions, but for now it is variable and seems to work fine. |
| Bug #: | 34 |
| Reporter: | Maciej Glowiak |
| Issue: | The wrong XML files to test the LS are being used. Instead of the newer LS files, older versions were included in the install package. |
| Fix: | The correct files were added, and names were changed. This also requires the eXist deploy script to be modified to insert a new collection. |
| RC3 Change: | The newer files were used (from the suggested directory) and the names of the files were changed to prevent confusion. The MA files also had the names changed. The respective scripts to run the client were also modified for the new names. In the course of using the new files, an unexpected problem occurred:
org.perfsonar.service.commons.exceptions.SystemException: [unknown]: XmlTypeLSServiceEngine: ActionType specified: LS_KEEPALIVE is not supported This was fixed easily enough by adding the proper handling code to the 'XmlTypeLSServiceEngine.java' file, and the Keepalive example works fine afterwords. The binary libraries were updated to go with the new change. |
| Bug #: | 35 |
| Reporter: | Maciej Glowiak |
| Issue: | $INSTALL_PATH variable does not change after initial set procedure in the graphical installer. |
| Fix: | The installer has been simplified somewhat, but the INSTALL_PATH still does not seem to update from panel to panel. This is not really a bug however, just a property of how IzPack operates. To simplify the install procedure I removed a lot of questions that will require a change to the variables, but some do still need to be there.
For the time being this does not seem to be too much of a hardship for the user, but we may move away from a graphical installer if there are enough complaints. A more important issue to deal with on the graphical installer front is the skipping of panel elements, which will be addressed in the next release. |
| RC3 Change: | Questions were removed, flow was adjusted. |
| Bug #: | 36 |
| Reporter: | Maciej Glowiak |
| Issue: | eXist installation scripts do not ask the user before destroying the old eXist database collections. |
| Fix: | There are two ways we can approach this one; Roman currently backs up the old collection as something else, or we can simply prompt to make sure the user is ok with us doing this. |
| RC3 Change: | This is a several stage fix:
1) First we prompt to make sure the user wants the configuration of eXist to go forward. 2) If we are configuring, we still make a backup and store it in the $INSTALL/conf directory. 3) A restore script is generated, in case the previous state of the DB is required. This will change the install process for both the text and graphical installers, and also both the LS and MA. |
| Bug #: | 33 |
| Reporter: | Vedrin Jeliazkov |
| Issue: | RRD MA begins registering with LS only after receiving/processing the first MetadataKeyRequest. |
| Fix: | It was suggested that a new version of axis may allow this to happen. As this is an enhancement it will be moved to the next RC and eventually to the trunk until it is voted on. |
| RC3 Change: | N/A |
[edit]
RC2 Suggested Enhancements
| Bug #: | Via E-Mail |
| Reporter: | Roman Lapacz |
| Issue: | The main install directory is cluttered, folders should be used to organize the scripts/text files, etc. |
| Fix: | Directory structure can be modified to allow for some better organization |
| RC3 Change: | A scripts directory was created, this contains all installer scripts as well as scripts created after the installation. |
| Bug #: | Via E-Mail |
| Reporter: | Roman Lapacz |
| Issue: | Too many questions, some not worthwhile (sax parser config, log4j into, etc.) |
| Fix: | Simplify the questions, use defaults. |
| RC3 Change: | Many questions were removed in both installers in favor of defaults. |
| Bug #: | Via E-Mail |
| Reporter: | Roman Lapacz |
| Issue: | Need a way to undeploy/deploy the installed service (a faster way at least, it is of course possible). |
| Fix: | Install some scripts to help the user. |
| RC3 Change: | Scripts are created as a part of the installation procedure. |
| Bug #: | Via E-Mail |
| Reporter: | Roman Lapacz |
| Issue: | Log file output doesn't contain timestamp info. |
| Fix: | Follow the format that is currently in the trunk. |
| RC3 Change: | The log file generation script now is created with timestamp info. |
[edit]
RC3 Bugs
| Bug #: | 39 |
| Reporter: | Maciej Glowiak |
| Issue: | After each installation two entries are added to catalina.properties (assuming you have the same tomcat all the time). We should remove old lines during the installation process before we add new entries. |
| Fix: | After backing up the old version, we should try to restore it to the state it was as it was first installed (without the added lines). A find/substitute will work well here to remove the old lines and extra whitespace, before the new things are added. |
| Release Change: | Added logic to the catalina shell scripts to clean up the file (after it has been backed up) so that only one service/components defn is included. |
| Bug #: | 40 |
| Reporter: | Luis Marta |
| Issue: | Readme.txt file contains instructions based on the wrong directory name for the axis installation directory. |
| Fix: | The readme should be changed to reflect the proper directory location. |
| Release Change: | The readme has been altered. |
| Bug #: | 41 |
| Reporter: | Roman Lapacz |
| Issue: | eXist installation script (when encountering previous installation of rrdmaconfig [presumable also ls]) does not seem to backup old copy. Installation 'completes' as well. |
| Fix: | The bug could not be replicated by the release team. The problem is believed to be related to eXist users and permissions. The eXist installation script was altered to now question for an eXist administrator password. This bug will be shelved, with the hope that we can either prove it wrong, or have some more evidence on other systems of a problem. |
| Release Change: | The eXist installation was altered, as well as a related question regarding a password was added to the installation scripts. |
| Bug #: | Reported via E-Mail |
| Reporter: | Miguel Baptista |
| Issue: | Readme.txt issues:
|
| Fix: | Edit readme file. |
| Release Change: | Changes where added. |
| Bug #: | Reported via E-Mail |
| Reporter: | Roman Lapacz |
| Issue: | Questions regarding log4j parameters are phrased wrong. |
| Fix: | Lookup exact meaning of the directives (provided by Roman) and edit questions. |
| Release Change: | Question text has been changed. |
