HIVE-2550,HIVE-2551: AWS deprov job compliant with cred proc#2325
HIVE-2550,HIVE-2551: AWS deprov job compliant with cred proc#2325openshift-merge-bot[bot] merged 2 commits intoopenshift:masterfrom
Conversation
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>
|
@celebdor: This pull request references HIVE-2551 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. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2325 +/- ##
==========================================
+ Coverage 58.54% 58.57% +0.03%
==========================================
Files 182 182
Lines 25843 25863 +20
==========================================
+ Hits 15130 15150 +20
Misses 9437 9437
Partials 1276 1276
|
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>
|
@celebdor: An error was encountered searching for bug HIVE-2551 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details. Full error message.
You do not have the permission to see the specified issue.: request failed. Please analyze the request body for more details. Status code: 401:
Please contact an administrator to resolve this issue, then request a bug refresh with 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. |
|
@celebdor: This pull request references HIVE-2550 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. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: celebdor, 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 |
|
/override "Red Hat Konflux / hive-on-pull-request" |
|
@lleshchi: Overrode contexts on behalf of lleshchi: Red Hat Konflux / hive-on-pull-request 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. |
|
/override "ci/prow/periodic-images" |
|
@lleshchi: Overrode contexts on behalf of lleshchi: ci/prow/periodic-images 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. |
|
@celebdor: all tests passed! 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 #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:
This commit fixes it by replicating the /output/hiveutil existance for deprovisioning in AWS (though it will only get used in STS mode).