Feature with 3 OT stages has 2 of them pointing to the same trial ID about chromium-dashboard HOT 4 CLOSED

Yep, I did the disconnection via pantheon and advised the feature owner as to their next steps on the blink-dev thread.

from chromium-dashboard.

The feature owner reported that the feature entry was back in the initial broken state today.
I investigated further and looked at the code for /cron/associate_origin_trials.

That code seems to correctly look for an existing OT stage that is already associated with the origin trial before trying to associate another stage on the same feature with that origin trial. So, it should not have reverted back to the broken state.

I looked at the datastore entries and found that the existing OT stage had the origin_trial_id set to the correct value but with type TEXT. That is not right because TEXT fields are not indexed and will not be found by the cron job when it searches for existing associated OT stages. It should be type STRING. I don't see anything in the code that ever used type TEXT. So, perhaps this was the result of a previous manual datastore edit.

In the pantheon UI, I set the value type to STRING and checked the checkbox to index it. After that, I ran the cron job twice and verified that it had correctly not associated the 3rd OT stage with the existing OT. This left the "Request Trial Creation" button available for the feature owner to press. I responded to the blink-dev thread again to explain and ask the feature owner to use the button.

from chromium-dashboard.

Assuming the problem here stems from the same cause as #3910, maybe we don't need any further investigation. @jrobbins can you disconnect the existing trial from the 3rd OT stage so that the owner can request a new trial creation?

from chromium-dashboard.

The user was able to request their new V3 OT.

from chromium-dashboard.