We have retrace02.qa.fedoraproject.org. ABRT does not used it for some time, but we want to use it now. I can ssh there through bastion, but I cannot get to the web interface. I think the attached patch can fix it. Can someone please review it?
<img alt="0001-retrace02.fedoraproject.org-as-alias-for-retrace02.q.patch" src="/fedora-infrastructure/issue/raw/files/e5aa39ec9996f66a62ca71069f8ae372f92476c9ebffc5d92eef87a8a0a6b4b0-0001-retrace02.fedoraproject.org-as-alias-for-retrace02.q.patch" />
So, do you want this machine to be reachable on https://retrace02.fedoraproject.org via our proxy network?
We need to:
Just let me know exactly what you want here and I can apply + do dns.
I need: some hostname, retrace02.f.o sounds just right. But it can be any other name as well. technically retrace02 is now not used for anything production, which makes it staging or development machine. So staging.
ok, so we mostly had stg setup already. We were pointing retrace.stg.fedoraproject.org to retrace01.stg.phx2.fedoraproject.org
I've changed it to point to retrace02.qa.fedoraproject.org now. It's not showing up however, as getting / on retrace02 is returning a 400 error currently and haproxy marks it down until thats working.
Should we delete the retrace01.stg vm ?
Hi Kevin, I am colleague of msuchy.
retrace02.qa.fedoraproject.org sounds just fine. If it is set up, retrace01.stg can be deleted.
Thank you
Done.
https://retrace.stg.fedoraproject.org goes to retrace02.qa.fedoraproject.org now.
I have removed retrace01.stg.phx2.fedoraproject.org
Let us know if there's anything more we can help with here.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Hmm, it seems that retrace02.qa.fedoraproject.org is not available. You mentioned that it is because it is returning 400, but I just connected to retrace02 and tried wget on http://localhost/faf and it worked as expected.
I am not sure right now, whether it is bug on our or your side. Can you check, as it seems that everything is working correctly on our side.
Thanks
Ah ha. I tracked this down to a firewall rule change that needs to happen in RHIT firewalls.
I have filed a ticket internally to get this opened up, will let you know when it's fixed.
Sorry for the issue.
This should be fixed now.
I tried it the same way as described in my last comment and still the same result. Does https://retrace02.qa.fedoraproject.org/faf work for you?
That url is not correct.
You want:
https://retrace.stg.fedoraproject.org/
This goes to our staging proxy httpd, which in turn goes to haproxy there, which in turn goes to retrace02.qa.fedoraproject.org.
Yes, sorry, you are correct.
It works, thank you so much!
Login to comment on this ticket.