Bug 2322373 - Update the section - Creating an AWS role using a script
Summary: Update the section - Creating an AWS role using a script
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: documentation
Version: 4.17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Kusuma
QA Contact: Neha Berry
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-10-29 08:08 UTC by Shira Dymnik
Modified: 2024-10-30 08:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OCSBZM-9446 0 None None None 2024-10-29 08:09:37 UTC

Description Shira Dymnik 2024-10-29 08:08:48 UTC
Describe the issue:
The service account name of statefulset-core.yaml was changed from "noobaa" to "noobaa-core" in version 4.17, therefore the script for creating the trust policy of the role should be updated and added this line, see:
https://github.com/noobaa/noobaa-operator/pull/1466/files

Describe the task you were trying to accomplish:
Fresh deployment of ODF in version 4.17 using AWS STS.

Suggestions for improvement:
Update the doc for version 4.17 to avoid any issues such as BZ 2322124:
https://bugzilla.redhat.com/show_bug.cgi?id=2322124#c5

Document URL:
https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.16/html-single/managing_hybrid_and_multicloud_resources/index#creating-an-aws-role-using-a-script_rhodf

Chapter/Section Number and Title:
Managing hybrid and multicloud resources
Chapter 3. Adding storage resources for hybrid or Multicloud
3.3.2. Creating an AWS-STS-backed backingstore 
3.3.2.1. Creating an AWS role using a script - here you need to edit

Product Version:
4.17

Environment Details:
OCP deployment on AWS STS cluster

Any other versions of this document that also needs this update:
If you have documentation about upgrade from 4.16 to 4.17 of ODF - then the user needs to update his existing trust policy and add the mentioned line to avoid issues.

Additional information:
Featiled information was raised in BZ 2322124


Note You need to log in before you can comment on or make changes to this bug.