No logging when traffic is routed to the default backend

[ilya-spv]

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT

NGINX Ingress controller version:
0.25.0

Kubernetes version (use kubectl version):
1.13.4

Environment:

• Azure AKS:

What happened:

When nginx controller redirects traffic to a default backend there was nothing written to the log

What you expected to happen:

I expect to see a log entry in the same format as when there is a request that is sent to one of the ingress routes.

How to reproduce it (as minimally and precisely as possible):

Go directly to the IP of the nginx ingress controller service (ExternalIP), the response is a 404 from a default backend or 200 if you go to externalIP/healthz.

Both request do not leave any trace in the logs.

Anything else we need to know:

There was already an issue before that should have been fixed in here.

Probably the bug is back in action after some updates.

[ar-qun]

I would also love to know more about this issue.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[ilya-spv]

/remove-lifecycle rotten

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[cep21]

I am able to reproduce in EKS using helm chart for nginx-ingress 1.34.2

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[Ufaowl]

I'm also having this issue. I get "default backend - 404" but zero info why

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[eliskovets]

/reopen

[k8s-ci-robot]

@eliskovets: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[vainu-lauri]

Let's try opening with (not sure if the bot allows).
We're seeing this with ngress-nginx-3.39. 0.49.3 as well

/remove-lifecycle rotten

[iamNoah1]

@vainu-lauri please open a new issue, also we are happy for any contributions :)