Reverted on the branch at https://chromium-review.googlesource.com/c/chromiumos/chromite/+/1359013

If this fixes the config-updater I will pass this bug on for what to do about ToT, we don't want to have to revert a CL on every branch so we need to get to the bottom of this.

In good news, reverting on the branch fixed the builder. 

https://ci.chromium.org/p/chromeos/builders/luci.chromeos.general/Prod/b8928132113251178976

So priority is lowered, we need to figure out how to instantiate this builder without it breaking on branches though...

The kevin64-full build works on TOT, but it's presence breaks on the release branch? That's.... new.

Was "kevin64" created through GE?

Yea, it has a construct on GE, it is just the addition of the kevin64-full that seems to have caused an issue. It seems like the config-updater does not like the Goldeneye config (which says kevin64 does not exist on the branch) being incongruent with the chromite config (which says kevin64-full should exist). 

I'm not sure why this is only a problem for kevin64. We've added/removed boards before.

I am curious why kevin64-full has a problem but kevin64-release builder is ok. Also, is there something that toolchain team can do here to avoid issues like this?

It's not a toolchain team issue, but a problem with how our branched build configs work.

A few thoughts here:

* We should identify the bug; if it's trivial, we should fix it.
* Medium term, GE will transition creating builders to DLM. When that happens, DLM will make a feed of which projects need builders and a continuously running CI job will establish builders by submitting CL's to both Buildbucket config and to Chromite. When that is implemented, config_updater will have to be shutdown and the functionality in GE will be removed in favor of DLM. Currently, that's looking like Q2.

I'm guessing the fix is to add the board to the hard coded list of boards in chromeos_config, and merge back to R72, but I'm not certain.