Closed Bug 1646809 Opened 4 years ago Closed 2 years ago

TreeHerder invalidates auth credentials after a few hours

Categories

(Tree Management :: Treeherder, defect)

defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1749962

People

(Reporter: kats, Unassigned)

References

Details

Attachments

(1 file)

This morning I was having trouble starring some try push failures on TreeHerder so I logged out and logged back in. Now it's been around 6 hours and again it gives me errors when I try to star failures. e.g. "Error saving classification for windows10-64-qr test-windows10-64-qr/debug-mochitest-browser-chrome-e10s-5: detail: Authentication credentials were not provided." It still shows me as logged in, and I can do other things like retrigger jobs just fine.

Also despite it showing the error about authentication credentials, it does seem to actually be recording my failure classifications, at least some of the time.

I'll look into this - someone else mentioned this problem today. Is this the first time you've had this problem?

If you see this again can you check if there is a message in the console or error messages in the networks tab? I wasn't able to reproduce this.

(In reply to Sarah Clements [:sclements] from comment #2)

I'll look into this - someone else mentioned this problem today. Is this the first time you've had this problem?

In general I get errors with TH complaining about credentials, but usually logging out/logging back in will fix it and keep it fixed for at least a couple of days. This problem seems new in the last week or so.

(In reply to Sarah Clements [:sclements] from comment #3)

If you see this again can you check if there is a message in the console or error messages in the networks tab? I wasn't able to reproduce this.

I don't see any errors the console, but I see a couple of 403 responses in the networks tab. I'll attach a screenshot, not sure if there's a way to copy the contents reasonably.

Thanks. I need to wrap up something else first but I'll prioritize improving/fixing this next week (see bug 1643117).

Assignee: nobody → sclements
Status: NEW → ASSIGNED

Thanks for working on this, Sarah. This bug hits me several times a day.

Assignee: sclements → nobody
Status: ASSIGNED → NEW
Status: NEW → RESOLVED
Closed: 2 years ago
Duplicate of bug: 1749962
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: