OCPBUGS-27489: Use correct hash sum of extracted tarball after re-signing with codesign

[ardaguclu]

When binaries are extracted via oc adm release extract command, we have to re-sign these binaries if the operating system is darwin and architecture is arm64. This manual re-signing process seems to be working well, at least we haven't gotten any issues so far. However, since we make modifications to tarball during the re-signing process, this changes the hash sum value of the tarball, whereas the value in sha256sum file refers to the hash sum of the tarball prior to re-sign process creates disperancy.

This PR writes modified tarball's hash sum value in sha256sum file to prevent mismatches.

This PR can be considered as a continuation of #1242

[openshift-ci-robot]

@ardaguclu: This pull request references Jira Issue OCPBUGS-27489, which is invalid:

• expected the bug to target the "4.16.0" version, 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.

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

In response to this:

When binaries are extracted via oc adm release extract command, we have to re-sign these binaries if the operating system is darwin and architecture is arm64. This manual re-signing process seems to be working well, at least we haven't gotten any issues so far. However, since we make modifications to tarball during the re-signing process, this changes the hash sum value of the tarball, whereas the value in sha256sum file refers to the hash sum of the tarball prior to re-sign process creates disperancy.

This PR writes modified tarball's hash sum value in sha256sum file to prevent mismatches.

This PR can be considered as a continuation of #1242

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.

[ardaguclu]

/jira refresh

[openshift-ci-robot]

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

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.16.0) matches configured target version for branch (4.16.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

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.

[ardaguclu]

/hold
I verified that this fix works properly but we still will need pre-merge testing.

[ardaguclu]

/retest

[zhouying7780]

/label qe-approved

[openshift-ci-robot]

@ardaguclu: This pull request references Jira Issue OCPBUGS-27489, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.16.0) matches configured target version for branch (4.16.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

In response to this:

When binaries are extracted via oc adm release extract command, we have to re-sign these binaries if the operating system is darwin and architecture is arm64. This manual re-signing process seems to be working well, at least we haven't gotten any issues so far. However, since we make modifications to tarball during the re-signing process, this changes the hash sum value of the tarball, whereas the value in sha256sum file refers to the hash sum of the tarball prior to re-sign process creates disperancy.

This PR writes modified tarball's hash sum value in sha256sum file to prevent mismatches.

This PR can be considered as a continuation of #1242

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.

[ardaguclu]

/hold cancel

[ardaguclu]

/cc @ingvagabund
Could you please take a look at, when you are available?. Thanks.

[ingvagabund]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ardaguclu, ingvagabund

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:

• pkg/cli/admin/release/OWNERS [ardaguclu]

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

[ardaguclu]

not related;
/retest-required

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 36702f9 and 2 for PR HEAD 93729f4 in total

[openshift-ci]

@ardaguclu: 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/test-infra repository. I understand the commands that are listed here.

[openshift-ci-robot]

@ardaguclu: Jira Issue OCPBUGS-27489: All pull requests linked via external trackers have merged:

• openshift/oc#1659

Jira Issue OCPBUGS-27489 has been moved to the MODIFIED state.

In response to this:

When binaries are extracted via oc adm release extract command, we have to re-sign these binaries if the operating system is darwin and architecture is arm64. This manual re-signing process seems to be working well, at least we haven't gotten any issues so far. However, since we make modifications to tarball during the re-signing process, this changes the hash sum value of the tarball, whereas the value in sha256sum file refers to the hash sum of the tarball prior to re-sign process creates disperancy.

This PR writes modified tarball's hash sum value in sha256sum file to prevent mismatches.

This PR can be considered as a continuation of #1242

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

[ART PR BUILD NOTIFIER]

This PR has been included in build openshift-enterprise-cli-container-v4.16.0-202401242108.p0.g34d0ed8.assembly.stream for distgit openshift-enterprise-cli.
All builds following this will include this PR.