Unable to activate challenge even it was created on legacy app.

[drasticdpk]

Steps

1. Go to https://challenges.topcoder.com/projects/24943/challenges/a630ae86-217d-44aa-9420-1000b8c00be5/view
2. Try to Activate

Reference

[vikasrohit]

@rootelement seems like API is always returning the same message even though the legacy is created. I guess, because of certain validations in legacy challenge, v4 ES index is not updated with the challenge and v4 api returns it as 404 because it reads the challenge from v4 ES.

[rootelement]

v4 api doesn't read from v4 es. It tries, but if it's not there, it fails over to reading from the db.

…

On Wed, Dec 9, 2020 at 8:35 AM vikasrohit ***@***.***> wrote: @rootelement <https://github.com/rootelement> seems like API is always returning the same message even though the legacy is created. I guess, because of certain validations in legacy challenge, v4 ES index is not updated with the challenge and v4 api returns it as 404 because it reads the challenge from v4 ES. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#950 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABJGMXFIRBHSW2JC6SKI64TST54JTANCNFSM4UTIUWRQ> .

-- James Cori Lead Software Engineer jcori@topcoder.com / 413.961.9044 / @jamesmcori <https://twitter.com/jamesmcori> <cbonner@topcoder.com>www.topcoder.com <http://topcoder.com/> / Topcoder Blog: topcoder.com/blog / twitter: @topcoder <https://twitter.com/topcoder>201 S Capitol Ave, Indianapolis, IN 46225

[ThomasKranitsas]

@rootelement the legacy.directProjectId needs to be updated by the sync tool when we bring a challenge forward to v5 from v4

[ThomasKranitsas]

We tested challenge activation a ton of times and never had any issues. It was the WM that was letting the user to "try" to activate without checking if the challenge is available on the legacy. I see that this is fixed now in the WM and you can't hit activate before the challenge is available on V5. We can close this issue.

Here's a sample challenge I tried just now https://challenges.topcoder-dev.com/projects/16640/challenges/151f3eff-f28e-4a29-91ff-9a255d9e4067/edit

cc @rootelement

[lakshmiathreya]

@ThomasKranitsas @rootelement - we did verify the challenge was updated on legacy ... yet WM was throwing up the above error ... it hasnt recurred since then ... I will watch this for some more time and close it ...

[vikasrohit]

@ThomasKranitsas issue is not that WM allowed to activate a challenge when the legacy was not created yet. However, the issue is that even after WM is showing that legacy is created (i.e. OR and Direct links are working), if you try to activate a challenge, for some particular use cases WM was showing the error shown in screenshot. And @mtwomey also faced this in his trail with WM last week and the fix that he did to resolve that was adding final deliverables to the legacy challenge in Direct and then the activate worked.
So, the root cause that we are debugging here is that for some situations it seems v5 api is throwing the same error as if the challenge is missing in legacy. And last night in discussions with @rootelement , we identified a possibility where due to some validation error (e.g. missing final deliverables) the challenge was not synced to the v4 ES and which in turn caused v5 api to think the challenge does not exist yet in legacy because v5 might be using the v4 API endpoint to check if legacy exists or not.
Does that help to understand the issue better?