Describe what you would like us to do:

I noticed that when the-new-hotness is trying to contact release-monitoring.org it starts getting timeouts. In the deployment config I noticed configuration of the hostname for release-monitoring.org:

        - hostnames:
          - release-monitoring.org
          ip: 10.5.126.8

I will gladly change it myself, I'm just not sure to which IP. Is this the IP that is shown in the openshift web console on pod details page? Or is this a different IP?

When do you need this to be done by? (YYYY/MM/DD)

pingou commented 3 years ago

So I was quickly looking into this:

$ host 10.5.126.8
8.126.5.10.in-addr.arpa domain name pointer proxy101.phx2.fedoraproject.org.

So it doesn't work because it's pointing to a proxy in phx2, which is now down, which means we need to point it to a proxy in iad2.

In ansible the file inventory/host_vars/proxy01.iad2.fedoraproject.org says this proxy has the IP address 10.3.163.74.

Maybe worth trying with this IP?

zlopez commented 3 years ago

I created a [PR]_https://pagure.io/fedora-infra/ansible/pull-request/135) with the new proxy IP and it helped :thumbsup:

Metadata Update from @zlopez:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

Metadata

Assignee

None

Tags

None

Blocking

None

Depending on

None

Priority

Needs Review

fedora-infrastructure

Source Code

#9033 the-new-hotness can't connect to release-monitoring.org on iad2 Closed: Fixed 3 years ago by zlopez. Opened 3 years ago by zlopez.

Describe what you would like us to do:

When do you need this to be done by? (YYYY/MM/DD)

Metadata

#9033 the-new-hotness can't connect to release-monitoring.org on iad2

Closed: Fixed 3 years ago by zlopez. Opened 3 years ago by zlopez.