Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1429382 - remove Amazon provider discovery as an option
remove Amazon provider discovery as an option
Status: CLOSED ERRATA
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers (Show other bugs)
5.6.0
Unspecified Unspecified
high Severity high
: GA
: 5.9.0
Assigned To: Julian Cheal
Matouš Mojžíš
provider:ec2
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-03-06 04:06 EST by Jiri Stefanisin
Modified: 2018-03-01 08:10 EST (History)
10 users (show)

See Also:
Fixed In Version: 5.9.0.2
Doc Type: Deprecated Functionality
Doc Text:
Discovery support for Amazon and Azure provider has been removed.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-03-01 08:10:28 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: AWS


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:0380 normal SHIPPED_LIVE Moderate: Red Hat CloudForms security, bug fix, and enhancement update 2018-03-01 13:37:12 EST

  None (edit)
Comment 11 Bronagh Sorota 2017-08-31 11:25:41 EDT
From Marcel to Brad and Bronagh via email on 8/30:


I think we could change the process to add all discovered ems's as paused
I've put an needinfo on https://bugzilla.redhat.com/show_bug.cgi?id=1343328 which is one of the old BZs wrt memory consumption of all created ems.

So, in case you dont want to scrap the feature, imho this is the way to remedy the problems caused by it, without a complete re-design of the UX around discovery
Comment 12 Bronagh Sorota 2017-08-31 11:26:44 EDT
Hi Brad,
How would you like to proceed?

thanks
Bronagh
Comment 23 Matouš Mojžíš 2018-02-07 09:17:43 EST
Verified in 5.9.0.20. Cloud discovery button is disabled.
Comment 26 errata-xmlrpc 2018-03-01 08:10:28 EST
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/RHSA-2018:0380

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