Unsetting repository architecture restriction doesn't reach clients
... because Candlepin never gets updated!
The candlepin db state can be verified with this query:
SELECT product.uuid AS "Product UUID", product.name AS "Product Name", product.product_id, content.content_id, content.uuid, content.label, content.name, content.arches FROM cp_pool pool JOIN cp2_products product ON pool.product_uuid = product.uuid JOIN cp2_product_content pc ON product.uuid = pc.product_uuid JOIN cp2_content content ON content.uuid = pc.content_uuid ORDER BY product.name ASC;
The implication of this change is that, for example: accidentally setting i386 architecture and then unsetting it will permanently lock the Content in Candlepin to i386 while the UI will show that no restriction is set because the RootRepository has the correct value. The workaround is to recreate the repo which is not ideal.
The fix should include a migration to update Candlepin to reflect whatever is currently set on the RootRepository