OCPBUGS-15347: Update version go-http-metrics/gin

[jkaurredhat]

go-http-metrics should be updated as this is pulling in the version of gin-gonic

In release-4.14
$ go mod graph | grep "gin-gonic/gin"
github.com/slok/[email protected] github.com/gin-gonic/[email protected]
github.com/slok/[email protected] github.com/gin-gonic/[email protected]
github.com/gin-gonic/[email protected] github.com/gin-contrib/[email protected]
github.com/gin-gonic/[email protected] github.com/go-playground/validator/[email protected]
github.com/gin-gonic/[email protected] github.com/golang/[email protected]
github.com/gin-gonic/[email protected] github.com/json-iterator/[email protected]
github.com/gin-gonic/[email protected] github.com/mattn/[email protected]
github.com/gin-gonic/[email protected] github.com/stretchr/[email protected]
github.com/gin-gonic/[email protected] github.com/ugorji/go/[email protected]
github.com/gin-gonic/[email protected] gopkg.in/[email protected]

$ grep go-http-metrics go.mod
github.com/slok/go-http-metrics v0.10.0 // indirect
In master branch the version with the fix is already being used.

$ grep go-http-metrics go.mod
github.com/slok/go-http-metrics v0.11.0 // indirect

[openshift-ci-robot]

@jkaurredhat: This pull request references Jira Issue OCPBUGS-15347, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-15347 to depend on a bug targeting a version in 4.15.0, 4.15.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

go-http-metrics should be updated as this is pulling in the version of gin-gonic

In release-4.14
$ go mod graph | grep "gin-gonic/gin"
github.com/slok/[email protected] github.com/gin-gonic/[email protected]
github.com/slok/[email protected] github.com/gin-gonic/[email protected]
github.com/gin-gonic/[email protected] github.com/gin-contrib/[email protected]
github.com/gin-gonic/[email protected] github.com/go-playground/validator/[email protected]
github.com/gin-gonic/[email protected] github.com/golang/[email protected]
github.com/gin-gonic/[email protected] github.com/json-iterator/[email protected]
github.com/gin-gonic/[email protected] github.com/mattn/[email protected]
github.com/gin-gonic/[email protected] github.com/stretchr/[email protected]
github.com/gin-gonic/[email protected] github.com/ugorji/go/[email protected]
github.com/gin-gonic/[email protected] gopkg.in/[email protected]

$ grep go-http-metrics go.mod
github.com/slok/go-http-metrics v0.10.0 // indirect
In master branch the version with the fix is already being used.

$ grep go-http-metrics go.mod
github.com/slok/go-http-metrics v0.11.0 // indirect

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]

Hi @jkaurredhat. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[jkaurredhat]

/jira refresh

[openshift-ci-robot]

@jkaurredhat: This pull request references Jira Issue OCPBUGS-15347, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected dependent Jira Issue OCPBUGS-43369 to target a version in 4.15.0, 4.15.z, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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.

[mhanss]

/label cherry-pick-approved

[jkaurredhat]

/jira refresh

[openshift-ci-robot]

@jkaurredhat: This pull request references Jira Issue OCPBUGS-15347, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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.

[bfournie]

/ok-to-test

[bfournie]

/test e2e-agent-ha-dualstack
/test e2e-agent-sno-ipv6

[openshift-ci]

@jkaurredhat: all tests passed!

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.

[jkaurredhat]

/cherrypick release-4.13

[openshift-cherrypick-robot]

@jkaurredhat: only openshift org members may request cherry picks. If you are already part of the org, make sure to change your membership to public. Otherwise you can still do the cherry-pick manually.

In response to this:

/cherrypick release-4.13

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.

[bfournie]

/lgtm

[rccrdpccl]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jkaurredhat, rccrdpccl

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [rccrdpccl]

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

[jkaurredhat]

/cherrypick release-4.13

[openshift-cherrypick-robot]

@jkaurredhat: only openshift org members may request cherry picks. If you are already part of the org, make sure to change your membership to public. Otherwise you can still do the cherry-pick manually.

In response to this:

/cherrypick release-4.13

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.

[bfournie]

/jira refresh

[openshift-ci-robot]

@bfournie: This pull request references Jira Issue OCPBUGS-15347, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.14.z) matches configured target version for branch (4.14.z)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-43369 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-43369 targets the "4.15.0" version, which is one of the valid target versions: 4.15.0, 4.15.z
• bug has dependents

Requesting review from QA contact:
/cc @mhanss

In response to this:

/jira refresh

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.