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 #7673 Git errors when creating repo and dumping ssh keys
    Actions
    Infos
    #7673
    Mohamed Amin Doghri (doghrim)
    2015-01-08 13:35
    2014-12-08 12:54
    7670
    Details
    Git errors when creating repo and dumping ssh keys
    Hello

    When I create a new Git repo I got following error in git_syslog but the repo is created under /var/lib/codendi/gitolite/repositories

    [error] [SystemEventProcessor] An error happened during execution of post actions: Command execution failure: git --work-tree='/var/lib/tuleap/gitolite/admin' --git-dir='/var/lib/tuleap/gitolite/admin/.git' push --porcelain origin master (return value: 1):
    error: Ref refs/heads/master is at 901d3e4c086a9079030f84a83321c0cd672c4e4f but expected 18e0a6c79b62322ade330b3692023f68776e48d8
    remote: error: failed to lock refs/heads/master
    error: failed to push some refs to 'gitolite@gl-adm:gitolite-admin'
    To gitolite@gl-adm:gitolite-admin
    ! refs/heads/master:refs/heads/master [remote rejected] (failed to lock)

    Also when trying to add a new ssh key, system event failed with following log but I can clone and push in my repos :
    "Could not dump ssh keys for user ..."
    Note that no error trace is logged in codendi_syslog nor git_syslog.

    Tuleap installed : Tuleap 7.7.99.51 in Centos 6.6

    Thanks to help
    Amin
    SCM/Git
    7.7
    CentOS 6
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Manuel Vacelet (vaceletm)
    Closed
    2015-01-08
    Attachments
    Artifact links
    Empty
    Empty
    References
    Referencing request #7673

    Artifact Tracker v5

    rel #7520 7.10

    Git commit

    tuleap/tuleap/stable

    Merge commit 'refs/changes/62/3362/4' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD a8a24a2035
    User avatar Yannis ROSSETTO (rossettoy) , 2015-01-08 13:34
    request #7673 Git errors when creating repo and dumping ssh keys c4abc64911
    User avatar Manuel Vacelet (vaceletm) , 2015-01-08 13:28
    request #7673 Git errors when creating repo and dumping ssh keys 30a0a88ca7
    User avatar Manuel Vacelet (vaceletm) , 2015-01-13 10:23
    Referenced by request #7673

    Other

    gerrit #3362
    Display settings

    Follow-ups

    User avatar
    Yannis ROSSETTO (rossettoy)2015-01-08 13:35
    Merged in Tuleap 7.9.99.8
    • Status changed from Under review to Closed
    • Close date set to 2015-01-08
    User avatar
    Mohamed Amin Doghri (doghrim)2014-12-11 17:58
    >>In prod re-run should be safe.
    Re-run of what ? If you mean system event, it's already "green" but log contain error.

    Thank you
    User avatar
    Manuel Vacelet (vaceletm)2014-12-11 16:27
    In prod re-run should be safe.

    Anyhow, the fix will be backported on tuleap enterprise release ASAP
    User avatar
    Mohamed Amin Doghri (doghrim)2014-12-11 16:19
    Thank you Manuel and Yannis ,

    @Manuel : "unix status" of my user was suspended that's why events (Edit SSH key) was failing , I just activate it and event passed, but I don't know why "unix status" is suspended by default , in fact I'm using LDAP for authentication with same parameters used in in our internal Tuleap.
    Also I don't know if LDAP daily synchro will suspend "unix status" or no (will be tested).

    For the other issue (refs/heads/master:refs/heads/master [remote rejected] (failed to lock)) what will be the impact if we encounter it on prod environment? Note that Git creation event "SystemEvent_GIT_REPO_UPDATE" is not failing in siteadmin interface despite the error displayed in log (codendi_syslog and git_syslog ).

    Thanks
    User avatar
    Manuel Vacelet (vaceletm)2014-12-11 11:19
    Actually this is issue (fail to lock) comes from concurrent git pushes.

    This comes from the new dedicated queues: all git events in one and other in "default queue".
    The bad thing is that EDIT SSH KEYS is done on "main queue" while the update of repo is done on git queue "at the same time".

    as a workaround you should be able to re-run the failed event
    • Status changed from New to Verified
    User avatar
    Manuel Vacelet (vaceletm)2014-12-11 11:07
    Did you made the 2 modifications "In a row" (Edit SSH key + create repo) ?

    For EDIT ssh key, what is the user account "unix status" ?