NO-JIRA: Log API request count when timestamp or user not available

[sanchezl]

• UPSTREAM: : log only deprecated api requests
• UPSTREAM: : log api req w/ ts and user not available

[openshift-ci-robot]

@sanchezl: This pull request explicitly references no jira issue.

In response to this:

• UPSTREAM: : log only deprecated api requests
• UPSTREAM: : log api req w/ ts and user not available

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@sanchezl: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 14596da|UPSTREAM: : log api req w/ ts and user not available: does not specify an upstream backport in the commit message
• 205c34a|UPSTREAM: : log only deprecated api requests: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sanchezl
Once this PR has been reviewed and has the lgtm label, please assign bertinatto for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• DOWNSTREAM_OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-merge-robot]

PR needs rebase.

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-sigs/prow repository.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle stale

[openshift-ci]

@sanchezl: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-agnostic-ovn-cmd	14596da	link	false	/test e2e-agnostic-ovn-cmd
ci/prow/k8s-e2e-gcp-serial	14596da	link	true	/test k8s-e2e-gcp-serial
ci/prow/e2e-gcp	14596da	link	true	/test e2e-gcp
ci/prow/e2e-gcp-ovn-upgrade	14596da	link	true	/test e2e-gcp-ovn-upgrade
ci/prow/e2e-aws-ovn-hypershift	14596da	link	true	/test e2e-aws-ovn-hypershift

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.