fix opentelemetry-cpp-contrib sha256

[esigo]

What this PR does / why we need it:

This PR fixes the sha256sum hash used in #8585.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation only

Which issue/s this PR fixes

How Has This Been Tested?

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I've read the CONTRIBUTION guide
• I have added tests to cover my changes.
• All new and existing tests passed.

[k8s-ci-robot]

@esigo: This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[k8s-ci-robot]

Hi @esigo. Thanks for your PR.

I'm waiting for a kubernetes 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/test-infra repository.

[longwuyuan]

/ok-to-test

@esigo is this sha good for 6 months, approximately

[longwuyuan]

/assign @rikatz

Ricardo, please advise if the merge of the previous opentelemetry PR should have fire cloudbuild or not.
Also, this PR merge should fire cloudbuild is it not ? Or is there something else needed to be done to fire cloudbuild ?

[esigo]

/ok-to-test

@esigo is this sha good for 6 months, approximately

@longwuyuan the sha should be good until you change the contrib commit hash.

ingress-nginx/images/opentelemetry/rootfs/build.sh

Line 129 in 24925cc

export OPENTELEMETRY_CONTRIB_COMMIT=6467ec2e4d67b08b44580b7eb7a298786f4eef91

[longwuyuan]

Thanks @esigo . What is your release cadence. Just trying to know when we will have to bump/change/update/pgrade.

[esigo]

Thanks @esigo . What is your release cadence. Just trying to know when we will have to bump/change/update/pgrade.

@longwuyuan we normally have monthly releases.

[rikatz]

/lgtm
/approve

Thanks

[rikatz]

@longwuyuan job was triggered and failed before: https://console.cloud.google.com/cloud-build/builds;region=global/431c55c4-f0bb-472c-acdd-1a43d6429ad0?project=k8s-staging-ingress-nginx

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: esigo, rikatz

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:

• images/OWNERS [rikatz]

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