[release-4.14] OCPBUGS-22539: otelhttp version upgrade to 0.44.0

[sunku5494]

List all the issues related to this PR

• New Feature
• Enhancement
• Bug fix
• Tests
• Documentation
• CI/CD

What environments does this code impact?

• Automation (CI, tools, etc)
• Cloud
• Operator Managed Deployments
• None

How was this code tested?

• assisted-test-infra environment
• dev-scripts environment
• Reviewer's test appreciated
• Waiting for CI to do a full test run
• Manual (Elaborate on how it was tested)
• No tests needed

Checklist

• Title and description added to both, commit and PR.
• Relevant issues have been associated (see CONTRIBUTING guide)
• This change does not require a documentation update (docstring, docs, README, etc)
• Does this change include unit-tests (note that code changes require unit-tests)

Reviewers Checklist

• Are the title and description (in both PR and commit) meaningful and clear?
• Is there a bug required (and linked) for this change?
• Should this PR be backported?

[openshift-ci-robot]

@sunku5494: This pull request references Jira Issue OCPBUGS-22539, which is invalid:

• expected the bug to target either version "4.18." or "openshift-4.18.", but it targets "4.14.z" instead

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:

List all the issues related to this PR

• New Feature
• Enhancement
• Bug fix
• Tests
• Documentation
• CI/CD

What environments does this code impact?

• Automation (CI, tools, etc)
• Cloud
• Operator Managed Deployments
• None

How was this code tested?

• assisted-test-infra environment
• dev-scripts environment
• Reviewer's test appreciated
• Waiting for CI to do a full test run
• Manual (Elaborate on how it was tested)
• No tests needed

Checklist

• Title and description added to both, commit and PR.
• Relevant issues have been associated (see CONTRIBUTING guide)
• This change does not require a documentation update (docstring, docs, README, etc)
• Does this change include unit-tests (note that code changes require unit-tests)

Reviewers Checklist

• Are the title and description (in both PR and commit) meaningful and clear?
• Is there a bug required (and linked) for this change?
• Should this PR be backported?

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sunku5494
Once this PR has been reviewed and has the lgtm label, please assign romfreiman 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:

• OWNERS

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

[openshift-ci-robot]

@sunku5494: This pull request references Jira Issue OCPBUGS-22539, 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-22539 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.

In response to this:

List all the issues related to this PR

• New Feature
• Enhancement
• Bug fix
• Tests
• Documentation
• CI/CD

What environments does this code impact?

• Automation (CI, tools, etc)
• Cloud
• Operator Managed Deployments
• None

How was this code tested?

• assisted-test-infra environment
• dev-scripts environment
• Reviewer's test appreciated
• Waiting for CI to do a full test run
• Manual (Elaborate on how it was tested)
• No tests needed

Checklist

• Title and description added to both, commit and PR.
• Relevant issues have been associated (see CONTRIBUTING guide)
• This change does not require a documentation update (docstring, docs, README, etc)
• Does this change include unit-tests (note that code changes require unit-tests)

Reviewers Checklist

• Are the title and description (in both PR and commit) meaningful and clear?
• Is there a bug required (and linked) for this change?
• Should this PR be backported?

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.

[sunku5494]

/test

[openshift-ci]

@sunku5494: The /test command needs one or more targets.
The following commands are available to trigger required jobs:

• /test e2e-agent-compact-ipv4
• /test images

The following commands are available to trigger optional jobs:

• /test e2e-agent-ha-dualstack
• /test e2e-agent-sno-ipv6
• /test push-pr-image

Use /test all to run the following jobs that were automatically triggered:

• pull-ci-openshift-assisted-service-release-4.14-e2e-agent-compact-ipv4
• pull-ci-openshift-assisted-service-release-4.14-images

In response to this:

/test

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-ci]

@sunku5494: 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/edge-e2e-nutanix-assisted-4-14	63c1f5a	link	false	/test edge-e2e-nutanix-assisted-4-14
ci/prow/images	63c1f5a	link	true	/test images
ci/prow/edge-e2e-ai-operator-disconnected-capi	63c1f5a	link	false	/test edge-e2e-ai-operator-disconnected-capi
ci/prow/edge-e2e-ai-operator-ztp-capi	63c1f5a	link	false	/test edge-e2e-ai-operator-ztp-capi
ci/prow/edge-lint	63c1f5a	link	true	/test edge-lint
ci/prow/edge-subsystem-aws	63c1f5a	link	true	/test edge-subsystem-aws
ci/prow/e2e-agent-compact-ipv4	63c1f5a	link	true	/test e2e-agent-compact-ipv4
ci/prow/edge-e2e-ai-operator-ztp	63c1f5a	link	true	/test edge-e2e-ai-operator-ztp
ci/prow/edge-e2e-oci-assisted	63c1f5a	link	false	/test edge-e2e-oci-assisted
ci/prow/mce-images	63c1f5a	link	true	/test mce-images
ci/prow/edge-e2e-metal-assisted-external	63c1f5a	link	false	/test edge-e2e-metal-assisted-external
ci/prow/edge-unit-test	63c1f5a	link	true	/test edge-unit-test
ci/prow/edge-images	63c1f5a	link	true	/test edge-images
ci/prow/edge-ci-index	63c1f5a	link	true	/test edge-ci-index
ci/prow/edge-e2e-vsphere-assisted	63c1f5a	link	false	/test edge-e2e-vsphere-assisted
ci/prow/edge-e2e-metal-assisted	63c1f5a	link	true	/test edge-e2e-metal-assisted
ci/prow/edge-subsystem-kubeapi-aws	63c1f5a	link	true	/test edge-subsystem-kubeapi-aws
ci/prow/images	63c1f5a	link	true	/test images
ci/prow/edge-e2e-oci-assisted-4-14	63c1f5a	link	false	/test edge-e2e-oci-assisted-4-14
ci/prow/e2e-agent-compact-ipv4	63c1f5a	link	true	/test e2e-agent-compact-ipv4
ci/prow/edge-e2e-nutanix-assisted	63c1f5a	link	false	/test edge-e2e-nutanix-assisted
ci/prow/edge-assisted-operator-catalog-publish-verify	63c1f5a	link	true	/test edge-assisted-operator-catalog-publish-verify
ci/prow/edge-verify-generated-code	63c1f5a	link	true	/test edge-verify-generated-code

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.

[sunku5494]

/jira refresh

[openshift-ci-robot]

@sunku5494: This pull request references Jira Issue OCPBUGS-22539, which is invalid:

• expected the bug to target only the "4.14.z" version, but multiple target versions were set
• expected Jira Issue OCPBUGS-22539 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.

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.

[sunku5494]

/jira refresh

[openshift-ci-robot]

@sunku5494: This pull request references Jira Issue OCPBUGS-22539, which is invalid:

• expected Jira Issue OCPBUGS-22539 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.

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.