)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"f3d9a8dc3e6ea3ac65d5a7d7d607451984d35b18","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"e0eabe79_7a145149","updated":"2025-02-25 19:59:35.000000000","message":"-1 for the gate-groups.yaml.j2 edit need. The other thought is more of a -0. I\u0027m ok with separate changes if others prefer it but I think I prefer one change.","commit_id":"b3f213d7c169678c259e7425574ec84910f6f054"},{"author":{"_account_id":7118,"name":"Ian Wienand","email":"iwienand@redhat.com","username":"iwienand"},"change_message_id":"c96921579b6ccb8d4250cfef57f27ad0cedc7557","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"9a07e2fc_6f3fdb85","updated":"2025-02-26 05:02:35.000000000","message":"Just a thought; we\u0027ve kept bridge pretty clean as a bastion host and out of the \"run something periodically\" department (i\u0027m thinking things like afsmon, mirror-update / afs releases / etc).\n\nThere is nothing secret about this list ... you can regenerate it from system-config.\n\nPerhaps crazy idea - attach the certcheck list as an artifact of infra-prod-letsencrypt job.\n\nThen, periodically run a job that gets that config from the latest job (`https://zuul.opendev.org/api/tenant/openstack/builds?job_name\u003dinfra-prod-letsencrypt\u0026project\u003dopendev/system-config\u0026limit\u003d1\u0026result\u003dSUCCESS`), run certcheck just in a regular job and then Zuul can email a failure to root?","commit_id":"b3f213d7c169678c259e7425574ec84910f6f054"}],"inventory/service/groups.yaml":[{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"f3d9a8dc3e6ea3ac65d5a7d7d607451984d35b18","unresolved":true,"context_lines":[{"line_number":48,"context_line":"    - backup01.ord.rax.opendev.org"},{"line_number":49,"context_line":"  cacti: cacti[0-9]*.open*.org"},{"line_number":50,"context_line":"  certcheck:"},{"line_number":51,"context_line":"    - bridge[0-9]*.opendev.org"},{"line_number":52,"context_line":"    - cacti[0-9]*.open*.org"},{"line_number":53,"context_line":"  cloud-launcher:"},{"line_number":54,"context_line":"    - bridge*.open*.org"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"0dabc6fc_10ececa0","line":51,"updated":"2025-02-25 19:59:35.000000000","message":"Now that we\u0027re adding bridge here we can remove it and the entire certcheck entry from playbooks/zuul/templates/gate-groups.yaml.j2. That way we\u0027re testing this change in the system-config-run jobs.\n\nSeparately, I think I have a slight preference for squashing this change and the child change together. That way we can remove cacti from this group in this same change then manually disable the cron on that server. That way we don\u0027t get alerts from cacti when the list there inevitably becomes stale. Additionally squashing ensures that bridge only ever uses the tool from distro packages and we don\u0027t have to clean up a git repo that isn\u0027t needed anymore.","commit_id":"b3f213d7c169678c259e7425574ec84910f6f054"}]}