Created attachment 1569214 [details] Adding an AWS Cloud Provider Description of problem: There are two place where an AWS region is selected, adding a new AWS Cloud Provider and scheduling database backups. The drop downs for selecting the region are different between the two. When adding an AWS Cloud Provider the regions are listed like "US East (N. Virginia) When adding a database backup schedule to an AWS S3 bucket the AWS Region drop down lists the regions like "us-east-1" At a minimum these drop-downs should display the regions in a consistent manner and preferably use the same UI component for rendering the drop-down. Version-Release number of selected component (if applicable): 5.10.3 How reproducible: Always Steps to Reproduce: 1. Add a new cloud provider of type AWS 2. Schedule a database backup to an AWS S3 bucket Actual results: drop-down list show different names for the regions Expected results: drop-down list should show the same names for the regions Additional info:
Created attachment 1569215 [details] Adding database backup to an AWS S3 bucket
https://github.com/ManageIQ/manageiq-ui-classic/pull/5606
New commit detected on ManageIQ/manageiq-ui-classic/master: https://github.com/ManageIQ/manageiq-ui-classic/commit/e9f56eff49b83bf4c65bf2e81c9c5a22eac6ef2a commit e9f56eff49b83bf4c65bf2e81c9c5a22eac6ef2a Author: Dávid Halász <dhalasz> AuthorDate: Mon May 20 08:38:01 2019 -0400 Commit: Dávid Halász <dhalasz> CommitDate: Mon May 20 08:38:01 2019 -0400 Make AWS region dropdown under schedules consistent with add provider Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1710623 app/controllers/ops_controller/settings/schedules.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Verified in 5.11.0.10. AWS Region drop-downs are consistent in CFME.
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-2019:4199