Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release-ocm-2.8] MGMT-15413: Use same installer binary for all platform types (#5334) #5408

Merged

Conversation

CrystalChun
Copy link
Contributor

@CrystalChun CrystalChun commented Aug 2, 2023

Cherry-pick of #5334
https://issues.redhat.com/browse/MGMT-15413

  • MGMT-15150: Use same installer binary for all platform types

There's nothing special about platform:none that requires it to use a different installer binary. This was originally done (in f9b2f3d) to avoid a problem with the openshift-baremetal-install binary not being available for non-x86 targets, but this was resolved by 1d025b8 (MGMT-9206).

  • Remove platform argument when extracting installer

Since we no longer use different installer binaries for different platforms, we no longer need to pass the platform type down. This allows us to clean up a lot of function signatures.

This partially reverts commit f9b2f3d.

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 openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 2, 2023
@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 2, 2023

@CrystalChun: This pull request references MGMT-15413 which is a valid jira issue.

In response to this:

Cherry-pick of #5334
https://issues.redhat.com/browse/MGMT-15413

  • MGMT-15150: Use same installer binary for all platform types

There's nothing special about platform:none that requires it to use a different installer binary. This was originally done (in f9b2f3d) to avoid a problem with the openshift-baremetal-install binary not being available for non-x86 targets, but this was resolved by 1d025b8 (MGMT-9206).

  • Remove platform argument when extracting installer

Since we no longer use different installer binaries for different platforms, we no longer need to pass the platform type down. This allows us to clean up a lot of function signatures.

This partially reverts commit f9b2f3d.

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 kubernetes/test-infra repository.

1 similar comment
@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 2, 2023

@CrystalChun: This pull request references MGMT-15413 which is a valid jira issue.

In response to this:

Cherry-pick of #5334
https://issues.redhat.com/browse/MGMT-15413

  • MGMT-15150: Use same installer binary for all platform types

There's nothing special about platform:none that requires it to use a different installer binary. This was originally done (in f9b2f3d) to avoid a problem with the openshift-baremetal-install binary not being available for non-x86 targets, but this was resolved by 1d025b8 (MGMT-9206).

  • Remove platform argument when extracting installer

Since we no longer use different installer binaries for different platforms, we no longer need to pass the platform type down. This allows us to clean up a lot of function signatures.

This partially reverts commit f9b2f3d.

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 kubernetes/test-infra repository.

@openshift-ci openshift-ci bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Aug 2, 2023
@codecov
Copy link

codecov bot commented Aug 2, 2023

Codecov Report

Merging #5408 (c5c9b78) into release-ocm-2.8 (b6735c2) will decrease coverage by 0.01%.
The diff coverage is 70.58%.

Additional details and impacted files

Impacted file tree graph

@@                 Coverage Diff                 @@
##           release-ocm-2.8    #5408      +/-   ##
===================================================
- Coverage            67.50%   67.49%   -0.01%     
===================================================
  Files                  218      218              
  Lines                32721    32721              
===================================================
- Hits                 22088    22086       -2     
- Misses                8641     8642       +1     
- Partials              1992     1993       +1     
Files Changed Coverage Δ
internal/bminventory/inventory.go 69.85% <ø> (-0.01%) ⬇️
internal/ignition/dummy.go 0.00% <0.00%> (ø)
internal/ignition/ignition.go 59.62% <0.00%> (ø)
internal/oc/release.go 71.83% <81.81%> (+0.11%) ⬆️
internal/installercache/installercache.go 70.51% <100.00%> (ø)

... and 1 file with indirect coverage changes

@CrystalChun
Copy link
Contributor Author

/cc @filanov

@openshift-ci openshift-ci bot requested a review from filanov August 2, 2023 15:54
https://issues.redhat.com/browse/MGMT-15413

---
MGMT-15150: Use same installer binary for all platform types (openshift#5334)

* MGMT-15150: Use same installer binary for all platform types

There's nothing special about platform:none that requires it to use a
different installer binary. This was originally done (in f9b2f3d) to
avoid a problem with the openshift-baremetal-install binary not being
available for non-x86 targets, but this was resolved by 1d025b8
(MGMT-9206).

* Remove platform argument when extracting installer

Since we no longer use different installer binaries for different
platforms, we no longer need to pass the platform type down. This allows
us to clean up a lot of function signatures.

This partially reverts commit f9b2f3d.
@CrystalChun
Copy link
Contributor Author

/retest-required

@openshift-ci
Copy link

openshift-ci bot commented Aug 3, 2023

@CrystalChun: 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 openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 3, 2023
@openshift-ci
Copy link

openshift-ci bot commented Aug 3, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: CrystalChun, filanov

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:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 3, 2023
@openshift-merge-robot openshift-merge-robot merged commit 602f258 into openshift:release-ocm-2.8 Aug 3, 2023
12 checks passed
@CrystalChun CrystalChun deleted the release-ocm-2.8 branch January 29, 2024 23:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants