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
MGMT-15150: Use same installer binary for all platform types #5334
Conversation
@zaneb: This pull request references MGMT-15150 which is a valid jira issue. In response to this:
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. |
@zaneb: This pull request references MGMT-15150 which is a valid jira issue. In response to this:
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. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #5334 +/- ##
==========================================
+ Coverage 67.55% 67.57% +0.02%
==========================================
Files 226 226
Lines 33227 33296 +69
==========================================
+ Hits 22446 22501 +55
- Misses 8763 8772 +9
- Partials 2018 2023 +5
|
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.
/test ? |
@eranco74: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
In response to this:
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. |
/test edge-e2e-metal-assisted-none |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: eranco74, zaneb 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 |
/cc @danielerez |
/lgtm |
@@ -6443,15 +6443,14 @@ func (b *bareMetalInventory) GetKnownApprovedHosts(clusterId strfmt.UUID) ([]*co | |||
return b.hostApi.GetKnownApprovedHosts(clusterId) | |||
} | |||
|
|||
// In case cpu architecture is not x86_64 and platform is baremetal, we should extract openshift-baremetal-installer | |||
// In case cpu architecture is not x86_64, we should extract openshift-baremetal-installer | |||
// from x86_64 release image as there is no x86_64 openshift-baremetal-installer executable in arm image. | |||
// This flow does not affect the multiarch release images and is meant purely for using arm64 release image with the x86 hub. | |||
// Implementation of handling the multiarch images is done directly in the `oc` binary and relies on the fact that `oc adm release extract` | |||
// will automatically use the image matching the Hub's architecture. | |||
func isBaremetalBinaryFromAnotherReleaseImageRequired(cpuArchitecture, version string, platform *models.PlatformType) bool { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The name of the func might be a bit confusing now... Maybe worth adding a comment about none platform clusters (i.e. that also the baremetal binary variant can be used).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's still the -baremetal- binary, so I think the name is still accurate.
TBH it might be less confusing than before, where the logic here said platform == baremetal and in the other location platform != none, and we were relying on the fact that no other platforms are supported on different architectures.
@zaneb: 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. |
/cherry-pick release-ocm-2.8 |
@filanov: #5334 failed to apply on top of branch "release-ocm-2.8":
In response to this:
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. |
…ft#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.
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.
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.
https://issues.redhat.com/browse/MGMT-15413 --- MGMT-15150: Use same installer binary for all platform types (#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. Co-authored-by: Zane Bitter <zbitter@redhat.com>
…ft#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.
…ft#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.
There's nothing special about platform:none that requires it to use a different installer binary. This was originally done 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). We no longer need all this complexity.
This partially reverts commit f9b2f3d.
List all the issues related to this PR
What environments does this code impact?
How was this code tested?
Checklist
docs
, README, etc)Reviewers Checklist