)]}'
{"doc/source/tenants.rst":[{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"335864a95c3b73d926e1856fc60d6fe5a6840813","unresolved":false,"context_lines":[{"line_number":34,"context_line":"changes to it are not read automatically. When the tenant"},{"line_number":35,"context_line":"configuration changes, it is necessary to signal a scheduler to read"},{"line_number":36,"context_line":"and apply the updated state. See the section on :ref:`reconfiguration`"},{"line_number":37,"context_line":"for instructions."},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Tenant"},{"line_number":40,"context_line":"------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"0d97cc3e_60dc24e0","line":37,"updated":"2022-02-15 19:53:25.000000000","message":"Oh, thanks, I was remembering where our deployment in OpenDev explicitly triggered a scheduler reconfigure any time a new copy of the tenant config was deployed to the server, but I probably missed that becoming obsolete at some point. I didn\u0027t realize addition and removal of projects to tenants has started automatically triggering tenant reconfiguration, though it looks like our current playbook still runs a smart-reconfigure as a handler any time we update main.yaml.","commit_id":"1dda5d7414dfae097846207a8bae503ce57a4ead"},{"author":{"_account_id":1,"name":"James E. Blair","email":"jim@acmegating.com","username":"corvus"},"change_message_id":"95391d8a47c952c817a1fea14b754777b6202c34","unresolved":false,"context_lines":[{"line_number":34,"context_line":"changes to it are not read automatically. When the tenant"},{"line_number":35,"context_line":"configuration changes, it is necessary to signal a scheduler to read"},{"line_number":36,"context_line":"and apply the updated state. See the section on :ref:`reconfiguration`"},{"line_number":37,"context_line":"for instructions."},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Tenant"},{"line_number":40,"context_line":"------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"cf4cb1ad_055c7dad","line":37,"updated":"2022-02-15 18:45:05.000000000","message":"We actually perform a smart reconfiguration event on startup of schedulers[1].  If there is a change to the tenant configuration (adding/removing projects/tenants), then those tenants should be reconfigured automatically.  However, if a change to in-repo zuul config was merged while all schedulers were offline, then a full or tenant reconfiguration would be needed in order for that to take effect.\n\nIt\u0027s not clear which thing you\u0027re trying to address here; if you have observed the first behavior in contradiction to what I wrote, we should look into that since it sounds like a bug.  If it\u0027s the second thing you want to communicate, then maybe we should elaborate a bit on this to make that clear.\n\n[1] https://opendev.org/zuul/zuul/src/branch/master/zuul/scheduler.py#L918-L925","commit_id":"1dda5d7414dfae097846207a8bae503ce57a4ead"}]}