Bug 1776637

Summary: Region for AWS not being passed to the operator while creating a backingstore.
Product: OpenShift Container Platform Reporter: Bipul Adhikari <badhikar>
Component: Console Storage PluginAssignee: Ankush Behl <anbehl>
Status: CLOSED ERRATA QA Contact: Anna Sandler <asandler>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.3.0CC: aos-bugs, asandler, ebenahar, nthomas
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1776660 (view as bug list) Environment:
Last Closed: 2020-05-04 11:17:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1776660    

Description Bipul Adhikari 2019-11-26 05:32:33 UTC
Description of problem:
Region value is not passed to operator while creating backingstore.


Version-Release number of selected component (if applicable):
4.3.0

How reproducible:
Easily


Steps to Reproduce:
1. Create an AWS backingsore with region value selected.


Actual results:
YAML doesn't have region value.

Expected results:
YAML should have region value.

Comment 2 Anna Sandler 2019-12-12 13:28:59 UTC
fixed. Created a AWS backing store using the UI: Operators -> Installed Operators -> Backing Store (on the top bar) -> create backing store -> set providers AWS S3 and specified a region -> create. In the yaml of the BS a region was specified successfully
(couldn't do that using CLI duo to some NooBaa CLI Problems) 

*same as bug #1776660

Comment 3 Elad 2019-12-12 13:34:07 UTC
Bipul, I changed the target release here to 4.4.0 as I believe this was the intention.

Comment 4 Bipul Adhikari 2019-12-18 04:16:05 UTC
Yes thanks Elad!

Comment 7 errata-xmlrpc 2020-05-04 11:17:08 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0581