Skip to content

HIVE-2548: backport AWS STS fixes#2332

Closed
celebdor wants to merge 3 commits intoopenshift:mce-2.6from
celebdor:HIVE-2548
Closed

HIVE-2548: backport AWS STS fixes#2332
celebdor wants to merge 3 commits intoopenshift:mce-2.6from
celebdor:HIVE-2548

Conversation

@celebdor
Copy link
Contributor

This is a manual backport for the AWS STS related fixes done in #2322 and #2325

2uasimojo and others added 3 commits June 25, 2024 23:09
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#2322, in order to fix AWS provisioining in STS mode we pointed the
credential_process configuration to /output/hiveutil. The problem is
that the same configuration is used for both provisioning and
deprovisioning. Thus, when trying to deprovision in STS mode, when it
came time for delegating operation to hiveutil, we'd get an:

    /output/hiveutil not found

This commit fixes it by replicating the /output/hiveutil existance for
deprovisioning in AWS (though it will only get used in STS mode).

Signed-off-by: Antoni Segura Puimedon <antoni@redhat.com>
There's a few conditions that make `ln` fail to create a hard link which
may be reproduced in a special volume like an emptyDir. The requirements
for a symlink are way lower.

Signed-off-by: Antoni Segura Puimedon <antoni@redhat.com>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 25, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 25, 2024

@celebdor: This pull request references HIVE-2548 which is a valid jira issue.

Details

In response to this:

This is a manual backport for the AWS STS related fixes done in #2322 and #2325

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-ci openshift-ci bot requested review from dlom and suhanime June 25, 2024 21:13
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 25, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: celebdor
Once this PR has been reviewed and has the lgtm label, please assign lleshchi for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details 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

@codecov
Copy link

codecov bot commented Jun 25, 2024

Codecov Report

Attention: Patch coverage is 95.45455% with 1 line in your changes missing coverage. Please review.

Project coverage is 58.58%. Comparing base (827f33b) to head (a076091).
Report is 30 commits behind head on mce-2.6.

Files with missing lines Patch % Lines
pkg/install/generate.go 95.45% 1 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##           mce-2.6    #2332      +/-   ##
===========================================
+ Coverage    58.55%   58.58%   +0.03%     
===========================================
  Files          182      182              
  Lines        25829    25849      +20     
===========================================
+ Hits         15124    15144      +20     
  Misses        9429     9429              
  Partials      1276     1276              
Files with missing lines Coverage Δ
pkg/install/generate.go 49.47% <95.45%> (+1.84%) ⬆️
---- 🚨 Try these New Features:

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 25, 2024

@celebdor: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/security a076091 link true /test security
ci/prow/e2e-pool a076091 link true /test e2e-pool

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 24, 2024
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 24, 2024
@openshift-merge-robot
Copy link
Contributor

PR needs rebase.

Details

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.

@openshift-bot
Copy link

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 24, 2024
@openshift-bot
Copy link

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci bot closed this Nov 24, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 24, 2024

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants