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 #42590 Random issue when updating tracker tickets after version upgrade
    Actions
    Infos
    #42590
    Oyabi (oyabi)
    2025-04-18 16:09
    2025-04-03 19:29
    44266
    Details
    Random issue when updating tracker tickets after version upgrade

    Hello,

    Since last week's version upgrade, we have been experiencing a recurring and random issue when updating tickets in the trackers.

    Observed symptoms:

    • When editing a ticket (changing status, adding a comment, updating a field), an error message appears: "Your request does not seem to be valid. Please try again."

    • This issue seems to occur mainly when the editing window has been left open for some time.

    • Users lose their input when they encounter this error.

    • Validating changes sometimes takes an unusually long time.

    • The issue has been observed by multiple users and appears to be random.

    Hypotheses:

    • A bug related to the recent version upgrade.

    • Possible synchronization issue between applications, causing performance problems.

    • Has anyone else encountered this behavior? Any leads on how to investigate or fix it?

    Thanks in advance for your help.

    Empty
    Empty
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Reopen
    Empty
    Attachments
    Artifact links

    Releases

    Fixed in

    Artifact ID Project Tracker Summary Status Last Update Date Submitted By Assigned to
    rel #41832 Tuleap Releases 16.7 Delivered 2025-04-23 15:25 Manuel Vacelet (vaceletm)
    Empty
    References
    Referencing request #42590

    Git commit

    tuleap/tuleap/stable

    fix: request #42590 Random issue when updating tracker tickets after version upgrade c27b7354a1
    User avatar Kevin Traini (ktraini) , 2025-04-14 10:57
    Merge commit 'refs/changes/63/34163/1' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD 788bcc4754
    User avatar Marie Ange Garnier (marieange) , 2025-04-14 12:07
    Display settings

    Follow-ups

    User avatar
    Marie Ange Garnier (marieange)2025-04-14 12:10

    Hello

    A fix have been integrated regarding this issue. If you still encounter problem after upgrade, feel free to re-open the artifact.

    Best regards

    User avatar
    François HAY (fhay_teliae)2025-04-11 11:53

    Hello

    We're still having the same issue with the CSRF token.

    This token is stored in Redis, and we've traced calls:

    root@TELv-Tuleap:/home/debug# grep 2cf186fabf1583aff955927dd011cbed log_jpe.log
    2025-04-10 14:20:31 : token testé: 2cf186fabf1583aff955927dd011cbed  token ref : 2cf186fabf1583aff955927dd011cbed  resultat : OK
    2025-04-10 17:05:05 : token testé: 2cf186fabf1583aff955927dd011cbed  token ref : 2cf186fabf1583aff955927dd011cbed  resultat : OK
    2025-04-10 17:06:04 : token testé: 2cf186fabf1583aff955927dd011cbed  token ref : 2cf186fabf1583aff955927dd011cbed  resultat : OK
    2025-04-11 10:19:35 : token testé: 2cf186fabf1583aff955927dd011cbed  token ref : caa6cc12fda75961dae5c44f256b6e76  resultat : KO
    root@TELv-Tuleap:/home/debug# grep caa6cc12fda75961dae5c44f256b6e76 log_jpe.log
    2025-04-11 10:19:35 : token testé: 2cf186fabf1583aff955927dd011cbed  token ref : caa6cc12fda75961dae5c44f256b6e76  resultat : KO
    2025-04-11 10:23:03 : token testé: caa6cc12fda75961dae5c44f256b6e76  token ref : caa6cc12fda75961dae5c44f256b6e76  resultat : OK
    2025-04-11 10:23:12 : token testé: caa6cc12fda75961dae5c44f256b6e76  token ref : caa6cc12fda75961dae5c44f256b6e76  resultat : OK
    2025-04-11 10:32:13 : token testé: caa6cc12fda75961dae5c44f256b6e76  token ref : caa6cc12fda75961dae5c44f256b6e76  resultat : OK
    2025-04-11 10:32:31 : token testé: caa6cc12fda75961dae5c44f256b6e76  token ref : caa6cc12fda75961dae5c44f256b6e76  resultat : OK
    2025-04-11 10:32:45 : token testé: caa6cc12fda75961dae5c44f256b6e76  token ref : caa6cc12fda75961dae5c44f256b6e76  resultat : OK
    2025-04-11 10:52:15 : token testé: caa6cc12fda75961dae5c44f256b6e76  token ref : caa6cc12fda75961dae5c44f256b6e76  resultat : OK
    2025-04-11 10:56:30 : token testé: caa6cc12fda75961dae5c44f256b6e76  token ref : caa6cc12fda75961dae5c44f256b6e76  resultat : OK
    root@TELv-Tuleap:/home/debug# grep cea47de16551376c4c0fcfc0e5813342 log_jpe.log
    2025-04-09 17:52:58 : token testé: cea47de16551376c4c0fcfc0e5813342  token ref : 9be9f50baae155f70a76834e63c71212  resultat : KO
    root@TELv-Tuleap:/home/debug# grep 9be9f50baae155f70a76834e63c71212 log_jpe.log
    2025-04-09 17:52:58 : token testé: cea47de16551376c4c0fcfc0e5813342  token ref : 9be9f50baae155f70a76834e63c71212  resultat : KO

    Thanks for your help

    User avatar
    Oyabi (oyabi)2025-04-04 19:27

    Hello,

    I encountered the invalid request error yesterday at around 4:53 PM and did some quick investigation to identify the potential cause.

    Findings:

    • The issue appears to be related to a security token expiration.

    • When editing a ticket, Tuleap sends a token named "challenge" in the body data of the request.

      • Example of such a request:
      ------geckoformboundaryb2dd38932d74b112854d11c898f8dec5
Content-Disposition: form-data; name="challenge"

6b2b0f2a2b76fa148646645e61038d51

    I noticed that my failed request had a different token compared to the successful one a few seconds later.

    By modifying the challenge value manually, I was able to reproduce the error message.

    This suggests that the issue is at least partially caused by an expired or invalid token. However, I’m not sure if this is the only source of the problem.

    Question:

    Would clearing the Tuleap cache help mitigate this issue? For example, can I safely delete the folder /var/tmp/tuleap_cache to refresh the stored data?

    Thanks in advance for your help!

    User avatar
    Manuel Vacelet (vaceletm)2025-04-04 09:11

    We don't experience the same kind of issues so it's unlikely to be version related (if you update today to 16.6.99.54+ for instance).

    The message you reference "Your request does not seem to be valid. Please try again." appears when the CSRF token of form has expired. It can happen when submitting a ticket if you let the artifact view open for hours and then submit. However it should not happen in regular usage.

    It might be related to an issue with session storage (in /var/tmp/tuleap_cache), if you encounter slowness, it's maybe because there is an issue with the filesystem.

    • Status changed from New to Waiting for information
    User avatar
    Oyabi (oyabi)2025-04-03 19:30
    • 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