Login failure

[tigersabre]

Describe the bug
After entering "tracetest start" I'm redirected to the web ui, but I get a failure message saying oauth has failed and to try again later.

To Reproduce
Steps to reproduce the behavior:

1. execute "tracetest start" command

Expected behavior
Log in to the webui to configure

Screenshots
If applicable, add screenshots to help explain your problem.

Browser (please complete the following information):
Chrome: Version 117.0.5938.92 (Official Build) (arm64)

Additional context
Add any other context about the problem here.

[kdhamric]

Reproduced this by signing in with a new user using Google Mail. My prior github account worked.

[tigersabre]

Yep, and now that Ive signed in with Google, my GitHub acct with same email is flagged as a duplicate.

…

On Thu, Oct 5, 2023, 2:57 p.m. kdhamric ***@***.***> wrote: Reproduced this by signing in with a new user using Google Mail. My prior github account worked. [image: image] <https://user-images.githubusercontent.com/1385894/273053999-3546a381-9f7c-465a-b0f9-84f2e34faa92.png> — Reply to this email directly, view it on GitHub <#3222 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABW4OCRKELIWUX3TIGKKSD3X54UNNAVCNFSM6AAAAAA5U5AANSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBZG4YDSNJQGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[jorgeepc]

Hey @tigersabre we identified the issue and the team is working on a fix. Will keep you posted.

[kdhamric]

@tigersabre I am now able to login with both my google and github account. I did have to:

• log out of app.tracetest.io (if you are logged in - you can do this at the top right)
• if you are on the mac, do a 'rm ~/.tracetest/config.yml'. You likely do not have one, but this resets your CLI to having no knowledge of an account with Tracetest.
• clear your cookies for app.tracetest.io
• try a 'tracetest start' again

The team will be looking at this further in the morning - sorry for the issue!

[kdhamric]

@tigersabre we believe it is corrected now. Can you let us know once you have tried again whether it is successful or not?

[jorgeepc]

This issue was fixed. We don't have new reports around this. I'm closing the ticket.