For osbs mutli arch, I need osbs-aarch64.stg.fedoraproject.org to point to the osbs-aarch64-master01.stg.arm.fedoraproject.org box.
Later when the prod cluster is running I ll need similar setup
When do you need this? (YYYY/MM/DD)
When is this no longer needed or useful? (YYYY/MM/DD)
If we cannot complete your request, what is the impact?
Proposed patch attached, I am not sure what should be the proxyurl there, I think it will also need a new dns entry.
<img alt="0001-OSBS-Configure-osbs-aarch64.fp.o-on-the-proxies.patch" src="/fedora-infrastructure/issue/raw/files/da575ef04de0997ebd1286296d121bcabd8d01238edac79f4f7a701e2a75a417-0001-OSBS-Configure-osbs-aarch64.fp.o-on-the-proxies.patch" />
Metadata Update from @bowlofeggs: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: OSBS
Metadata Update from @smooge: - Issue assigned to smooge
As suggested by @kevin I have tried to use the internal name https://osbs-aarch64-master01.stg.arm.fedoraproject.org:8443 since this is only needed for osbs clusters to communicate together.
But I think now the firewall is blocking the requests between osbs-master01.stg.phx2.fedoraproject.org and osbs-aarch64-master01.stg.arm.fedoraproject.org
osbs-master01.stg.phx2.fedoraproject.org
osbs-aarch64-master01.stg.arm.fedoraproject.org
If I try curl --connect-timeout 30 https://osbs-aarch64-master01.stg.arm.fedoraproject.org:8443 on osbs-master01.stg.phx2.fedoraproject.org it is timing out.
curl --connect-timeout 30 https://osbs-aarch64-master01.stg.arm.fedoraproject.org:8443
ok, so do we only need https here? I could file a ticket asking for that...
so I ll need port 8443 to be open also from osbs-node01.stg.phx2.fedoraproject.org and osbs-node02.stg.phx2.fedoraproject.org
Metadata Update from @cverna: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.