HIVE-2548: Run installmanager binary in install container for fips compatibility#2260
HIVE-2548: Run installmanager binary in install container for fips compatibility#22602uasimojo merged 3 commits intoopenshift:mce-2.6from
Conversation
|
Skipping CI for Draft Pull Request. |
|
/test all |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## mce-2.6 #2260 +/- ##
========================================
Coverage 58.54% 58.55%
========================================
Files 182 182
Lines 25830 25829 -1
========================================
+ Hits 15123 15124 +1
+ Misses 9431 9429 -2
Partials 1276 1276
|
|
/test all |
|
/test all |
1 similar comment
|
/test all |
|
/retest e2e |
|
@lleshchi: The
Use
DetailsIn 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 e2e |
1 similar comment
|
/test e2e |
2c3d29f to
f581d13
Compare
|
/test all |
|
/assign @2uasimojo |
2uasimojo
left a comment
There was a problem hiding this comment.
I have substantive concerns over cert installation. We should ask QE for a pre-merge run that specifically targets that path.
These concerns have been assuaged. But...
...we should still totally do this. From our conversation: I think we want to make sure QE hits e.g. this path by making sure |
2uasimojo
left a comment
There was a problem hiding this comment.
I think this is ready to go
/lgtm
but
/hold
cause we want to do some pre-merge QE.
As a result of the openshift installer transitioning from rhel8 to rhel9 (openshift/installer#8196), running openshift-install in the rhel8 backed hive container in order to install a cluster in fips mode results in a fips incompatibility. Create a seperate installmanager binary that runs the install-manager command previously invoked by hiveutil. Build a rhel8 and rhel9 version of hive, and copy both versions of installmanager to the installer container. The directory struture of the provisioning pod is also adjusted to support this change. Lastly, the installmanager binary corresponding to the rhel version of the installer container. Signed-off-by: Leah Leshchinsky <lleshchi@redhat.com>
Signed-off-by: Leah Leshchinsky <lleshchi@redhat.com>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 2uasimojo, lleshchi The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
1 similar comment
|
/retest |
|
/test e2e |
|
/test e2e e2e-pool Looks like new permission requirements were added: I've added these to the |
|
/override ci/prow/security |
|
@2uasimojo: Overrode contexts on behalf of 2uasimojo: ci/prow/security DetailsIn 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-sigs/prow repository. |
|
/test e2e e2e-pool I... must not have hit the final "go" button on those permissions? |
|
Same error, but now I know for sure the perms are there. WTF? /test e2e e2e-pool |
|
/test e2e-pool infra flake |
|
I forgot again that our CI user is in a different AWS account. /test e2e e2e-pool |
|
/test e2e-pool |
1 similar comment
|
/test e2e-pool |
|
/test e2e-pool same infra flake -- opening DPTP request |
|
/retitle HIVE-2548: Run installmanager binary in install container for fips compatibility |
|
@lleshchi: This pull request references HIVE-2548 which is a valid jira issue. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@lleshchi: This pull request references HIVE-2548 which is a valid jira issue. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
1 similar comment
|
@lleshchi: This pull request references HIVE-2548 which is a valid jira issue. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/test e2e-pool |
|
@lleshchi: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
In openshift#2260 we changed how we're invoking the openshift-install binary. Before: Copy openshift-install into the hive container and run it via `/usr/bin/hiveutil install-manager` After: Copy hiveutil into the installer container and run installer via `/output/hiveutil.rhel$VER install-manager` What we missed was that, for STS flows, we inject an AWS credentials file containing a `credential_process` that invoked `/usr/bin/hiveutil install-manager aws-credentials` -- but `hiveutil` no longer lives there. Fix. HIVE-2400
In openshift#2260 we changed how we're invoking the openshift-install binary. Before: Copy openshift-install into the hive container and run it via `/usr/bin/hiveutil install-manager` After: Copy hiveutil into the installer container and run installer via `/output/hiveutil.rhel$VER install-manager` What we missed was that, for STS flows, we inject an AWS credentials file containing a `credential_process` that invoked `/usr/bin/hiveutil install-manager aws-credentials` -- but `hiveutil` no longer lives there. Fix. HIVE-2400
In openshift#2260 we changed how we're invoking the openshift-install binary. Before: Copy openshift-install into the hive container and run it via `/usr/bin/hiveutil install-manager` After: Copy hiveutil into the installer container and run installer via `/output/hiveutil.rhel$VER install-manager` What we missed was that, for STS flows, we inject an AWS credentials file containing a `credential_process` that invoked `/usr/bin/hiveutil install-manager aws-credentials` -- but `hiveutil` no longer lives there. Fix. HIVE-2400
In openshift#2260 we changed how we're invoking the openshift-install binary. Before: Copy openshift-install into the hive container and run it via `/usr/bin/hiveutil install-manager` After: Copy hiveutil into the installer container and run installer via `/output/hiveutil.rhel$VER install-manager` What we missed was that, for STS flows, we inject an AWS credentials file containing a `credential_process` that invoked `/usr/bin/hiveutil install-manager aws-credentials` -- but `hiveutil` no longer lives there. Fix. HIVE-2400
HIVE-2400
HIVE-2548