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 #24182 Failing start run to dead lock
    Actions
    Infos
    #24182
    Guilhem Bonnefille (CS) (gbonnefille)
    2021-11-29 17:04
    2021-11-25 20:28
    25723
    Details
    Failing start run to dead lock

    When an error occurs during the initial setup of the first deployment:

    1. setup starts, initiating passwords and DB schema
    2. setup fails (for some reason) -> so nothing is copied to persistency, but DB does in its side
    3. restart -> setup starts (again) initiating passwords (with new values), detect the DB exists, but fails to connect as the new password is used but does not match the actual one in the database.

    This tuleapadm password seems to be a technical account. It is only used to let Tuleap access database. One simple solution could be to force the update of the tuleapadm password in database:

    • each time it is changed by the setup process
    • or even simply each time the container boots
    Docker images
    13.2
    EL7 (CentOS|RHEL)
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Acknowledged
    Empty
    Attachments
    Artifact links
    Empty
    Empty
    References
    References list is empty
    Display settings

    Follow-ups

    User avatar
    Manuel Vacelet (vaceletm)2021-11-29 17:04

    Thanks for the report, we will see how we can take this scenario into account

    • Status changed from New to Acknowledged