Right now a single update-graph is cached in the graph-builder, and the service assumes it only contains x86_64 details.
Not what FCOS is publishing aarch64 streams too, we should split and cache the graphs separately.
Caches should be effectively partitioned according to the (architecture, stream) tuple, and for the current scenario we are going to end up with 6 caches: [x86_64, aarch64] x [stable, testing, next].
Right now a single update-graph is cached in the graph-builder, and the service assumes it only contains x86_64 details. Not what FCOS is publishing aarch64 streams too, we should split and cache the graphs separately. Caches should be effectively partitioned according to the
(architecture, stream)tuple, and for the current scenario we are going to end up with 6 caches:[x86_64, aarch64] x [stable, testing, next].