Known Issues and workarounds

In this topic:

Known issues

This section includes the known issues when working with the current GitCentric release:

• 636910 - Git push fails due to presence of pipes (|) in http request

  Due to a CVE-2016-6816 fix, when Tomcat is configured with GitCentric, the "|" character is disallowed, leading to HTTP 400 errors while performing push operations.

  Workaround: Enable configuration in <tomcat_home>/conf/catalina.properties, as follows: tomcat.util.http.parser.HttpParser.requestTargetAllow=|. Restart the Tomcat server.

• 24861 - Change package gaps

  If you use change packages (CPKs) with GitCentric in AccuRev 5.7 or earlier, be aware that GitCentric does not currently span CPK gaps automatically. This is not an issue in AccuRev 6.0 owing to changes in CPK functionality.

• 27473 -- email confirmation

  GitCentric currently does not provide confirmation email for account verification.

• 27790 - Authorization

  GitCentric currently supports onlyAccuRev authentication (that is, GitCentric users must have a valid AccuRev account). GitCentric does not currently support other authorization types such as LDAP, OpenID, etc.

• 28936 - kandoMaintain backup files

  The kandoMaintain backupdbs command creates backup files in the same directory as the kandoMaintain.jar, not where kandoMaintain is run from.

• 29070 - Re-installs require Tomcat reboot

  If you re-install GitCentric over an existing installation, sometimes you cannot log into GitCentric when the installation is done. To fix this, restartTomcat(<tomcat_home>/bin/shutdown.sh, followed by <tomcat_home>/bin/startup.sh).

• 29564 - Register all IP addresses for a server

  For security reasons, the GitCentric bridge accepts commands only from IP addresses that it recognizes. If you have registered an AccuRev server that has multiple IP addresses (for example, if the server has multiple Ethernet cards) you must add server entries for each IP address. In this case, you should perform GitCentric operations only against one of these servers entries -- typically one where you have specified a host name rather than an IP address. If you have a situation where IP addresses can change over time (such as dynamic IP addresses assigned via DNS), you may need to consider setting AC_BRIDGEAPI_SECURITY_POLICY to AllowAnyHost. Note, however, that this workaround has a security impact that you need to carefully consider before implementing it.

  Procedures for adding server entries and GitCentric configuration settings are documented in the AccuRev Help Center.

• 29089 - Errors in catalina.out log file

  You may see instances of “SEVERE” errors in catalina.out, relating to “failure to unregister JDBC driver” and “remove threads on exit”. These errors can be safely ignored in this release.

• 30954 - Some strings with special characters require quote marks

  A known issue with Gerrit requires that you enclose certain values in gerrit.config and secure.config files in double quotes if they contain special characters, as summarized in the following table. This table lists the values that require double quotes for special characters:

  Config File	Section	Value
  gerrit.config	[gerrit]	basepath
  	[httpd]	listenURL
  	[kando]	KANDOHOME bridgeURL
  secure.config	[database]	password

  For example, if the password in your secure.config file is my!pass#ord, you would need to enclose it in double quotes: password = "my!pass#ord". The gerrit.config and secure.config files are located in <gc_home>/site/etc.

• 31660 -- Code Review

  GitCentric Code Review submit/merge operations do not return issues that have been closed in change comments.

Back to top

Gerrit Issues

Since GitCentric (GC) incorporates Gerrit Code Review, see Troubleshooting code review for problems that you might encounter while using Gerrit Code Review in GitCentric.

Back to top

Workarounds

You may you encounter the following error when trying to clone/pull/push or execute an ssh command against the GC server: "Unable to negotiate with <GC host> port 29418: no matching key exchange method found."

This problem can either be solved with a workaround on each client that experiences the problem, or with one work-around on the GitCentric server.

Solution on client

1. Create a file config: Run <text editor> ~/.ssh/config.

2. Ensure that the line below are added in the file config :

   Host *

   KexAlgorithms diffie-hellman-group1-sha1

   Note: This works for Linux client or Windows client with Git for windows only. It does not work for built - in Git, such as TortoiseGit or the Eclipse Git plug-in.

Solution on server

The solution is to add the 'bouncy castle' jars to the project. Bouncy Castle is an open source encryption library.

The three jars to be added to the project are (155 indicates the version number):

• bcpg-jdk15on-155.jar
• bcpkix-jdk15on-155.jar
• bcprov-ext-jdk15on-155.jar

Download the bouncy castle jar files. Copy the three jar files to <tomcat install>/lib

Note: Installing the jar files in this location might require re -configuration of other Web applications supported by the same Tomcat server.

Back to top