On Mon, Sep 06, 2021 at 08:01:40PM +0200, Adrian Reber wrote:
Over the last weeks we prepared adding CentOS Stream to Fedora's
MirrorManager instance and are now at a point where we would like to
push the changes to ansible.
The current state can be seen at:
http://mirrors.stg.centos.org/metalink?repo=centos-baseos-9-stream&ar...
(https just broke over the weekend)
I fixed that. Sorry about that. ;(
To enable CentOS Stream in MirrorManager not only configuration file
changes are necessary, but it also requires an update of all software
components. This is mainly due to the fact that CentOS Stream is using
an empty topdir. (topdir in MirrorManager are things like 'epel/' or
'fedora/linux' or 'fedora-secondary/').
Unfortunately all code assumed that topdir is not '' and hard-coded the
removal of a slash all over the place.
All corresponding projects have been update to handle empty topdirs.
To apply
https://pagure.io/fedora-infra/ansible/pull-request/775 for
prod I need this FBR.
Also this may need a bit more work on proxies.
Something like:
diff --git a/playbooks/include/proxies-reverseproxy.yml
b/playbooks/include/proxies-reverseproxy.yml
index d771a0144..a2e0788cd 100644
--- a/playbooks/include/proxies-reverseproxy.yml
+++ b/playbooks/include/proxies-reverseproxy.yml
@@ -366,7 +366,6 @@
website:
mirrors.centos.org
destname: mirrormanager-mirrorlist
proxyurl:
http://localhost:10002
- when: env == "staging"
- role: httpd/reverseproxy
website:
download.fedoraproject.org
diff --git a/playbooks/include/proxies-websites.yml
b/playbooks/include/proxies-websites.yml
index 99fef15cb..fb144733f 100644
--- a/playbooks/include/proxies-websites.yml
+++ b/playbooks/include/proxies-websites.yml
@@ -158,8 +158,7 @@
server_aliases:
-
mirrors.stg.centos.org
cert_name: "{{mirrors_centos_org_cert_name}}"
- SSLCertificateChainFile: mirrors.stg.centos.org.intermediate.cert
- when: env == "staging"
+ SSLCertificateChainFile:
"mirrors{{env_suffix}}.centos.org.intermediate.cert"
- role: httpd/website
site_name:
src.fedoraproject.org
There are risks doing code changes like this during a freeze. So far I
have not seen any problems in staging, but staging is not using using
MirrorManager as thoroughly as prod. I don't expect any major problems
with this change.
I hope someone from the CentOS team can weigh if this is very time
critical to get running or if we can wait until after the freeze.
I think it would be safe to do at this point, but if we can hold off
until after freeze thats of course great.
kevin