Bug 2322373

Summary: Update the section - Creating an AWS role using a script
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Shira Dymnik <sdymnik>
Component: documentationAssignee: Kusuma <kbg>
Status: VERIFIED --- QA Contact: Neha Berry <nberry>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.17CC: ebenahar, odf-bz-bot, shirshfe
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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