fedora-infrastructure

#6463 openshift stg network issue?
Closed: Fixed Opened by ralph.

Closed: Fixed
Reopen Issue

My issue is that stg greenwave cannot talk to stg resultsdb.

https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=461f7cc

I'm on os-node01.stg.phx2.fedoraproject.org which should be 10.5.128.104 and I can't curl curl http://resultsdb-stg01.qa.fedoraproject.org/resultsdb_api/api/v2.0/results which resolves to 10.5.124.147 on that box.

However, I can curl https://taskotron.stg.fedoraproject.org/resultsdb_api/api/v2.0/results which resolves to 209.132.181.5 on that box.

but, when I enter a container on os-master01.stg with oc rsh dc/greenwave-fedmsg-consumer, I am unable to curl either address.

I assume this is because some special internal dns zone-ing isn't available inside the container image?

/cc @mjia, @dcallagh, @puiterwijk, @codeblock

Metadata Update from @codeblock:
- Issue assigned to codeblock

Fixed by https://infrastructure.fedoraproject.org/cgit/dns.git/commit/?id=9e7868b

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

Repointed stg greenwave at stg resultsdb: https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=b69d359940bb2283b755e43b0b9c31c6c8db7158
Metadata
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.