Bug 1671844 - [RFE] Remove GCE Provider
Summary: [RFE] Remove GCE Provider
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: API
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.11.0
Assignee: drew uhlmann
QA Contact: Mike Shriver
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-01 20:42 UTC by Loic Avenel
Modified: 2019-12-12 13:35 UTC (History)
12 users (show)

Fixed In Version: 5.11.0.13
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-12 13:35:22 UTC
Category: Feature
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:4199 0 None None None 2019-12-12 13:35:36 UTC

Description Loic Avenel 2019-02-01 20:42:58 UTC 
Description of problem: Remove CGE Provider
Comment 13 Jason Frey 2019-05-30 15:26:55 UTC 
Renamed the title as it is misleading.  Provider has already been disabled, but the API needs to prevent adding it.

The API issue should probably be a separate BZ because it's likely a systemic issue, not a GCE specific issue.  That is, I bet you can add *any* disabled provider at the moment.
Comment 14 drew uhlmann 2019-06-06 17:58:57 UTC 
https://github.com/ManageIQ/manageiq/pull/18842
Comment 16 Mike Shriver 2019-07-17 02:27:13 UTC 
Tested in CFME 5.11.0.14

The GCE provider add via REST now returns 400 response containing "Api::BadRequestError: Could not create the new provider - Validation failed: emstype ManageIQ::Providers::Google::CloudManager is not supported for create"
Comment 18 errata-xmlrpc 2019-12-12 13:35:22 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-2019:4199
Note You need to log in before you can comment on or make changes to this bug.