Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #9664 Gerrit Integration Troubles
    Actions
    Infos
    #9664
    Kelly Ferrone (kferrone)
    2016-11-26 08:44
    2016-11-19 02:13
    9942
    Details
    Gerrit Integration Troubles

    We are having some troubles trying to get the Gerrit installation to work. 

    Below is the error I get when I try "Migrate Repo to Gerrit"

    • Cannot connect to remote Gerrit server Gerrit REST driver: an error occured while checking existance of project ([curl] 60: [url] https://gerrit.mysite.com/a/projects/lab%2FGitTuleapTester)

    Hoping someone can help guide me a bit with this integration. I followed the instructions as best I could at the url below.

    Our Gerrit version is 2.13.2 with all core plugins and we have LDAP Auth successfully working on Gerrit and Tuleap. SSL is all working on a wildcard on both servers with same domain. 

    I did not go through the "Setup parent projects(Umbrella)" section because it did not seem necessary, correct me if I'm wrong. 

    Where it got a bit confusing is the section called "Configure gerrit replication." It asks me to inflate the plugin with the following command:

    gerrit@gerrit.instance.com$ unzip -j gerrit.war WEB-INF/plugins/replication.jar -d gerrit_testsite/plugins/

    I already have this plugin installed because it asked me to install while installing gerrit. Do I need this step still? I simply made made the "replication.config" file and added what was provided with the correct URL. 

    I also skipped the section called "Configure the email of the administrator." It also did not seem 100% necessary, correct me if I'm wrong. 

    Anyone have any similar issues? Anyone have any idea of what I could try to find out more about the problem? 

    SCM/Gerrit
    9.1
    CentOS 6
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Closed
    2016-11-26
    Attachments
    By Kelly Ferrone (kferrone)
    (51 kB)
    gerrit-config-tuleap.png
    What I have with some alterations for posting online
    References
    References list is empty
    Display settings

    Follow-ups

    User avatar
    Nicolas Terray (nterray)2016-11-26 08:44
    Great! I'm closing the request then.
    • Status changed from Waiting for information to Closed
    • Close date set to 2016-11-26
    User avatar
    Kelly Ferrone (kferrone)2016-11-21 23:20

    You are right. Seems to be something with Root certificates. I've seen issues like this before on other servers. I think I know what to do, I'll try and let you know. Below is the output from the command you gave. 

    [root@tuleap ~]# curl -v https://gerrit.mydomain.com
    * About to connect() to gerrit.mydomain.com port 443 (#0)
    *   Trying 111.111.111.11... connected
    * Connected to gerrit.mydomain.com (111.111.111.11) port 443 (#0)
    * Initializing NSS with certpath: sql:/etc/pki/nssdb
    *   CAfile: /etc/pki/tls/certs/ca-bundle.crt
      CApath: none
    * Peer's certificate issuer is not recognized: 'CN=COMODO RSA Domain Validation Secure Server CA,O=COMODO CA Limited,L=Salford,ST=Greater Manchester,C=GB'
    * NSS error -8179
    * Closing connection #0
    * Peer certificate cannot be authenticated with known CA certificates
    curl: (60) Peer certificate cannot be authenticated with known CA certificates
    More details here: http://curl.haxx.se/docs/sslcerts.html

    curl performs SSL certificate verification by default, using a "bundle"
     of Certificate Authority (CA) public keys (CA certs). If the default
     bundle file isn't adequate, you can specify an alternate file
     using the --cacert option.
    If this HTTPS server uses a certificate signed by a CA represented in
     the bundle, the certificate verification probably failed due to a
     problem with the certificate (it might be expired, or the name might
     not match the domain name in the URL).
    If you'd like to turn off curl's verification of the certificate, use
     the -k (or --insecure) option.

    User avatar
    Thomas Gerbet (tgerbet)2016-11-21 09:46
    The curl error 60 indicates there is an issue with the validation of the certificate. You probably do not provide the full certificates chain.

    Do you also have an issue when you run curl -v https://gerrit.example.com from the Tuleap server?
    • Status changed from New to Waiting for information
    User avatar
    Kelly Ferrone (kferrone)2016-11-19 02:22
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes