I don't know when this problem started (I'm pretty sure a week ago Bodhi staging was running), but since few days some staging apps are down due to what it seems a DNS problem (reason: DNS Config Forming ).
For example, in Bodhi staging: Search Line limits were exceeded, some search paths have been omitted, the applied search line is: bodhi.svc.cluster.local svc.cluster.local cluster.local iad2.fedoraproject.org vpn.fedoraproject.org fedoraproject.org
Search Line limits were exceeded, some search paths have been omitted, the applied search line is: bodhi.svc.cluster.local svc.cluster.local cluster.local iad2.fedoraproject.org vpn.fedoraproject.org fedoraproject.org
For review-stats the same error is displayed: Search Line limits were exceeded, some search paths have been omitted, the applied search line is: review-stats.svc.cluster.local svc.cluster.local cluster.local iad2.fedoraproject.org vpn.fedoraproject.org fedoraproject.org
Search Line limits were exceeded, some search paths have been omitted, the applied search line is: review-stats.svc.cluster.local svc.cluster.local cluster.local iad2.fedoraproject.org vpn.fedoraproject.org fedoraproject.org
Oh, I forgot about the planned outage of the last weekend. Maybe this problem is due to #9439
I'm getting timeout for https://stg.release-monitoring.org, but I'm not sure if this is related.
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: medium-gain, medium-trouble, ops
When trying it again, I noticed the issue with https://stg.release-monitoring.org is not related. So please ignore my previous comment.
These
bodhi.svc.cluster.local svc.cluster.local cluster.local
are domains I am not sure are going to work unless this is local to OpenShift itself. I don't know what fills out domains (/etc/resolv.conf or related files for systemd-resolvd) for containers.
yes, openshift has it's own nameserver and resolves those itself. ;)
Those search limit messages are a harmless warning that has been happening since we installed our first cluster. ;)
The problem here is likely at the proxy level. it's not perhaps got the right ip for stg.release-monitoring.org or it's not doing a seperate cert for it or something.
Things were down because somehow it wasn't using the persistent registry so they needed to do new builds after the recent reboots. ;(
I fired off builds for everything that was in imagepullbackoff.
bodhi is up now. Does everything look ok for you now? If not, let me know specifically which app and what you are seeing and we can investigate more.
Things were down because somehow it wasn't using the persistent registry so they needed to do new builds after the recent reboots. ;( I fired off builds for everything that was in imagepullbackoff. bodhi is up now. Does everything look ok for you now? If not, let me know specifically which app and what you are seeing and we can investigate more.
Thanks, everything works now. I did try to fire a new build for review-stats before opening this ticket, but for some reason it didn't work in my case... didn't try for Bodhi though.
Metadata Update from @mattia: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Issue status updated to: Open (was: Closed)
Issue status updated to: Closed (was: Open) Issue close_status updated to: Fixed
Login to comment on this ticket.