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 #11384 After-Upgrade "password_configuration table is missing" ?
    Actions
    Infos
    #11384
    Anton KULIK (d00AK)
    2018-04-11 11:48
    2018-04-11 09:35
    11705
    Details
    After-Upgrade "password_configuration table is missing" ?
    Current state:
    01) performed upgrade this morning
    02) after upgrade script shows "password_configuration table is missing" error (screenshot)

    Question
    What are the implications of this?
    Upgrade process
    development
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Closed
    2018-04-11
    Attachments
    Artifact links

    Releases

    Fixed in

    Artifact ID Project Tracker Summary Status Last Update Date Submitted By Assigned to
    rel #10995 Tuleap Releases 10.0 Delivered 2018-26-04 12:21 Manuel Vacelet (vaceletm)
    By Anton KULIK (d00AK)
    (122 kB)
    Screenshot 2018-04-11 09.33.38.png
    password table error
    By Anton KULIK (d00AK)
    (91 kB)
    Screenshot 2018-04-11 11.10.15.png
    password_configuration
    References
    Referenced by request #11384

    Artifact Tracker v5

    rel #10995 10.0
    Display settings

    Follow-ups

    User avatar
    Thomas Gerbet (tgerbet)2018-04-11 11:48
    Fix has been merged, the package forgeupgrade-1.5-1 including the fix is propagating to the RPM repositories.
    • Status changed from Under review to Closed
    • Connected artifacts
    • Close date set to 2018-04-11
    User avatar
    Thomas Gerbet (tgerbet)2018-04-11 11:12
    Yes, the table has been created.
    There is only an error in the script checking if the table has effectively been created. The table always appear missing even when properly created that's why you see an error when running the upgrade process.
    User avatar
    Thomas Gerbet (tgerbet)2018-04-11 10:41
    Hello,

    I have been able to reproduce the issue. Check in your DB if the password_configuration table is present, if it is everything should be fine.
    It seems to be an issue with the migration script, I'm working on a fix.
    • Status changed from New to Verified
    • Reported in version changed from 9.19 to development